From: Jeff Garzik <jgarzik@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dontdiff for 2.6.0-test4
Date: Mon, 01 Sep 2003 22:47:00 -0400 [thread overview]
Message-ID: <3F5404A4.4080700@pobox.com> (raw)
In-Reply-To: <7vk78rykzb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I do not think it is a tangent. While I am not opposed to ship
> dontdiff under Documentation/* separately from the current
> mrproper implementation in the Makefile, if these two should
> name the identical set of paths, coming up with a scheme in
> which humans have to maintain just a single source and derive
> these two different usage from that single source would make
> people's life easier. Two things that should be identical but
> have to be kept in sync by hand is simply a maintenance
> headache.
The two are maintained separately now. This is changing a file location
to make things a bit more convenient for dontdiff users; it's not
radically changing anything, technically or politically.
If there are persons that consider the presence of dontdiff in the tree
a maintenance headache, then those persons should not patch dontdiif.
Problem solved :) It's a file that's not going change often.
> On the other hand, if there are paths that should be in dontdiff
> that should not be cleaned by mrprper, or vice versa, then
> keeping two separately and maintaining two independently would
> absolutely makes sense. Are there such cases?
People are thinking _way_ too hard about this. This is just plunking a
rarely-changing file into the kernel tree. Even implying some sort of
maintenance hassle is making a mountain out of a molehill.
Jeff
next prev parent reply other threads:[~2003-09-02 2:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 14:57 dontdiff for 2.6.0-test4 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 [this message]
2003-09-02 5:55 ` Junio C Hamano
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=3F5404A4.4080700@pobox.com \
--to=jgarzik@pobox.com \
--cc=junkio@cox.net \
--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