From: Junio C Hamano <junkio@cox.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dontdiff for 2.6.0-test4
Date: Mon, 01 Sep 2003 22:55:17 -0700 [thread overview]
Message-ID: <7vfzjfybsq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <3F5404A4.4080700@pobox.com> (Jeff Garzik's message of "Mon, 01 Sep: 47:00 -0400")
>>>>> "JG" == Jeff Garzik <jgarzik@pobox.com> writes:
JG> People are thinking _way_ too hard about this. This is just plunking
JG> a rarely-changing file into the kernel tree. Even implying some sort
JG> of maintenance hassle is making a mountain out of a molehill.
The last sentence I agree---it is really not a big deal. But if
the thing is rarely changed, more likely people would forget to
update one when changing the other, wouldn't they?
In any case, either the dontdiff and mrproper are maintained
separately or not, I am in favor of having dontdiff in the
kernel tree.
prev parent reply other threads:[~2003-09-02 5:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 14:57 Tigran Aivazian
2003-09-01 15:39 ` Christoph Hellwig
2003-09-01 15:51 ` Tigran Aivazian
2003-09-01 16:12 ` Jeff Garzik
2003-09-01 16:09 ` Maciej Soltysiak
2003-09-01 16:15 ` Tigran Aivazian
2003-09-01 16:22 ` Sam Ravnborg
2003-09-01 16:54 ` Herbert Poetzl
2003-09-01 17:07 ` Jeff Garzik
2003-09-01 17:18 ` Sam Ravnborg
2003-09-01 21:47 ` Mike Fedyk
2003-09-01 22:29 ` Charles Lepple
2003-09-02 1:24 ` Jeff Garzik
2003-09-02 4:05 ` Sam Ravnborg
[not found] ` <fa.ebr1o03.l4o1q3@ifi.uio.no>
2003-09-02 2:36 ` Junio C Hamano
2003-09-02 2:47 ` Jeff Garzik
2003-09-02 5:55 ` Junio C Hamano [this message]
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=7vfzjfybsq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®