From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
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: Mon, 29 Jun 2009 18:30:27 -0700 [thread overview]
Message-ID: <4A496AB3.8030008@zytor.com> (raw)
In-Reply-To: <20090627074706.GA30839@uranus.ravnborg.org>
Sam Ravnborg wrote:
>
> Convinced with respect to the *.gz *.bz2 *.lzma or *.cpio extensions.
> But I will continue to be reluctant to adding global entries,
> as I have been beated from time to time by something
> that was ignored but should not have been so.
>
In general, in the particular case of the Linux kernel tree, I think
that it's generally safe to add binary file types to the top level: we
have *extremely* few binary files in the tree, and those are clearly
special cases.
Text files or ambiguous types is another matter.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-06-30 1:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 20:52 [PATCH] gitignore: add *.bz2 and *.cpio to top-level; clean up usr/ 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
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 [this message]
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=4A496AB3.8030008@zytor.com \
--to=hpa@zytor.com \
--cc=benh@kernel.crashing.org \
--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=sam@ravnborg.org \
--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