[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090626224321.GA27310@uranus.ravnborg.org>
Date: Sat, 27 Jun 2009 00:43:21 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Jaswinder Singh Rajput <jaswinder@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Randy Dunlap <randy.dunlap@...cle.com>,
Russell King <rmk+lkml@....linux.org.uk>,
benh@...nel.crashing.org, paulus@...ba.org
Subject: Re: [PATCH] gitignore: add *.bz2 and *.cpio to top-level; clean up usr/
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists