From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Tigran Aivazian <tigran@veritas.com>,
linux-kernel@vger.kernel.org, tigran@aivazian.fsnet.co.uk
Subject: Re: dontdiff for 2.6.0-test4
Date: Mon, 01 Sep 2003 21:24:18 -0400 [thread overview]
Message-ID: <3F53F142.5050909@pobox.com> (raw)
In-Reply-To: <20030901171806.GB1041@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Mon, Sep 01, 2003 at 01:07:41PM -0400, Jeff Garzik wrote:
>
>>dontdiff must know about many things that 'make mrproper' need not care
>>about:
>>
>> files with ".bak" suffix
>> files with "~" suffix
>> BitKeeper, CVS, RCS, SCCS directories
>
>
> make mrproper already cares about all those.
> Fragments from top-level Makefile:
I stand corrected :) However, I think it's a tangent:
dontdiff is a file that's useful precisely because of the form its in.
So, as something that's proven itself useful to a bunch of people, I
definitely think it has a home somewhere in Documentation/* It need not
be referenced in any way by kbuild; that's not a big deal. The two
really serve different purposes.
Jeff
next prev parent reply other threads:[~2003-09-02 1:24 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 [this message]
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
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=3F53F142.5050909@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tigran@aivazian.fsnet.co.uk \
--cc=tigran@veritas.com \
/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