From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752395Ab0CJKLo (ORCPT ); Wed, 10 Mar 2010 05:11:44 -0500 Received: from qw-out-2122.google.com ([74.125.92.26]:23192 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751323Ab0CJKLj convert rfc822-to-8bit (ORCPT ); Wed, 10 Mar 2010 05:11:39 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VKcSLXaqp6X9CkQ15k1hY5QAJFBlwZIp2FmSAtmwqWS4pXm2wno/9+Pv1YZcsnqysU qKXZIn2XFnr4Lkicj39M8+4P5drmfG8JQVMsmp3Rbi3HCVfjDBirIthU5EN6MlzuNBEK zhZscM3/df7ze5Dqj6g3gtPzj7TvRBxMI/Pqo= MIME-Version: 1.0 In-Reply-To: References: <4B90CBE5.9090102@viscovery.net> <1267780845-10547-1-git-send-email-jslaby@suse.cz> <4B9120F2.2020000@gmail.com> Date: Wed, 10 Mar 2010 18:11:38 +0800 Message-ID: <2375c9f91003100211vbe66a49g1bec37b2dcf609c2@mail.gmail.com> Subject: Re: [PATCH 1/1] gitignore: do not ignore include/linux/ From: =?UTF-8?Q?Am=C3=A9rico_Wang?= To: David Rientjes Cc: Linus Torvalds , Jiri Slaby , Jakub Narebski , Jiri Slaby , Andrew Morton , git@vger.kernel.org, linux-kernel@vger.kernel.org, Johannes Sixt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 10, 2010 at 6:07 PM, David Rientjes wrote: > On Fri, 5 Mar 2010, Jiri Slaby wrote: > >> On 03/05/2010 11:43 AM, Jakub Narebski wrote: >> >> +!/.gitignore >> >> +!/.mailmap >> > >> > Actually you want to *not ignore* .gitignore and .mailmap (and >> > .gitattributes which is missing here) anywhere, not only as top-level >> > file.  So .gitignore and .mailmap should not be prepended with slash. >> >> >> > > Please either revert 3b2a8c8f3c65 or merge the fixed up patch for > 2.6.34-rc2, otherwise include/linux will continue to be ignored by git > just like it is for 2.6.34-rc1. Why not apply the patch from Jiri? Since this problem is introduced by new version of git, not that commit.