From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: Rutger Nijlunsing <rutger@nospam.com>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [2.6 patch] ppc .gitignore update
Date: Wed, 1 Aug 2007 07:53:28 -0600 [thread overview]
Message-ID: <fa686aa40708010653v7e1fb909gb03eb1d4754359bf@mail.gmail.com> (raw)
In-Reply-To: <20070801133056.GP3972@stusta.de>
On 8/1/07, Adrian Bunk <bunk@stusta.de> wrote:
> arch/ppc/.gitignore shouldn't exclude arch/ppc/boot/include
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> ---
> --- /dev/null 2006-09-19 00:45:31.000000000 +0200
> +++ linux-2.6.23-rc1-mm2/arch/ppc/boot/.gitignore 2007-08-01 15:18:33.000000000 +0200
> @@ -0,0 +1 @@
> +!include
I don't think this is the best way to go about it; rather,
arch/ppc/.gitignore should be made more specific like so:
diff --git a/arch/ppc/.gitignore b/arch/ppc/.gitignore
index a1a869c..1e79a0a 100644
--- a/arch/ppc/.gitignore
+++ b/arch/ppc/.gitignore
@@ -1 +1 @@
-include
+/include
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-08-01 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 13:30 [2.6 patch] ppc .gitignore update Adrian Bunk
2007-08-01 13:53 ` Grant Likely [this message]
2007-08-01 19:06 ` Adrian Bunk
2007-08-01 20:20 ` MPC83xx - previous patch to set MBAR Keith Mund
2007-08-02 0:20 ` Kim Phillips
2007-08-02 2:14 ` [U-Boot-Users] " Liu Dave-r63238
2007-08-02 2:34 ` Alfred Manheim
2007-08-02 15:28 ` Scott Wood
2007-08-02 16:12 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2007-08-21 16:57 [2.6 patch] ppc .gitignore update Adrian Bunk
2007-08-22 4:54 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa686aa40708010653v7e1fb909gb03eb1d4754359bf@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rutger@nospam.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).