From: Baruch Siach <baruch@tkos.co.il>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] remove redundant .gitignore entries
Date: Mon, 13 Dec 2010 14:33:28 +0200 [thread overview]
Message-ID: <20101213123328.GD5766@jasper.tkos.co.il> (raw)
In-Reply-To: <20101213120857.GH6017@pengutronix.de>
Hi Sascha,
On Mon, Dec 13, 2010 at 01:08:57PM +0100, Sascha Hauer wrote:
> On Mon, Dec 13, 2010 at 08:00:10AM +0200, Baruch Siach wrote:
> > The ARCH and CROSS_COMPILE entries were introduced in commit cdfd8bdd, probably
> > by mistake.
>
> 'redundant' seems to imply that these are duplicates, but they are not.
English is not my native language. I couldn't come up with anything better.
> They were also not introduced by accident. I use a wrapper script for
> make which evaluates these files, so I'd like to keep them, although
> they are only for my personal use.
The .git/info/exclude file is a better place for local excludes, IMHO. I use
it myself for this.
baruch
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > .gitignore | 2 --
> > 1 files changed, 0 insertions(+), 2 deletions(-)
> >
> > diff --git a/.gitignore b/.gitignore
> > index 6f04601..cdc4df0 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> > @@ -34,8 +34,6 @@ barebox.netx
> > barebox.map
> > System.map
> > Module.symvers
> > -ARCH
> > -CROSS_COMPILE
> > barebox_default_env
> >
> > #
> > --
> > 1.7.2.3
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-12-13 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 6:00 Baruch Siach
2010-12-13 12:08 ` Sascha Hauer
2010-12-13 12:33 ` Baruch Siach [this message]
2010-12-13 13:10 ` Sascha Hauer
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=20101213123328.GD5766@jasper.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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