From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Russell King <rmk+lkml@arm.linux.org.uk>,
benh@kernel.crashing.org, paulus@samba.org
Subject: Re: [PATCH] gitignore: add *.bz2 and *.cpio to top-level; clean up usr/
Date: Sat, 27 Jun 2009 00:43:21 +0200 [thread overview]
Message-ID: <20090626224321.GA27310@uranus.ravnborg.org> (raw)
In-Reply-To: <4A454A69.4050301@zytor.com>
On Fri, Jun 26, 2009 at 03:23:37PM -0700, H. Peter Anvin wrote:
> Sam Ravnborg wrote:
> >
> > I would prefer to have *.gz and *.lzma pushed out to the
> > directories where it matters.
> > There global ignore rules will bite us one day.
> >
> > So I did not apply neither this nor Peter's original patch.
> >
>
> I think that's the wrong answer, unless we somehow end up with
> compressed files in the source. At the moment, a *.gz file in the
> source tree is much more likely to be a file in use by the developer.
My concern is that we may decide to carry files in certain formats
in the kernel source.
And I see a tendency to add more and more file extensions to the
top-level .gitignore file.
It is fine as long as this is files that are:
1) either generated in a lot of places
2) or generated in the top-level directory
But files that we generate in a few arch/*/boot/ directories
does not belong in the top-level .gitignore file.
We should keep the ignore rules close to where they apply,
even if this may cause us to add a few more lines
to the relevant .gitignore files.
Sam
next prev parent reply other threads:[~2009-06-26 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 20:52 H. Peter Anvin
2009-06-21 7:32 ` Jaswinder Singh Rajput
2009-06-26 22:21 ` Sam Ravnborg
2009-06-26 22:23 ` H. Peter Anvin
2009-06-26 22:43 ` Sam Ravnborg [this message]
2009-06-26 22:51 ` H. Peter Anvin
2009-06-27 7:47 ` Sam Ravnborg
2009-06-27 8:41 ` Jaswinder Singh Rajput
2009-06-30 1:30 ` H. Peter Anvin
2009-06-26 22:30 ` H. Peter Anvin
2009-06-26 22:31 ` Jaswinder Singh Rajput
2009-06-26 22:46 ` Sam Ravnborg
2009-06-26 22:51 ` Jaswinder Singh Rajput
2009-06-26 22:26 ` Jaswinder Singh Rajput
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=20090626224321.GA27310@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=benh@kernel.crashing.org \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=randy.dunlap@oracle.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome