linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Lepple <clepple@ghz.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: dontdiff for 2.6.0-test4
Date: Mon, 01 Sep 2003 18:29:37 -0400	[thread overview]
Message-ID: <bj0h8a$ev5$1@sea.gmane.org> (raw)
In-Reply-To: <20030901214738.GF31760@matchmail.com>

Mike Fedyk wrote:
[...]
>>mrproper:
>>        @find . $(RCS_FIND_IGNORE) \
>>                \( -name '*.orig' -o -name '*.rej' -o -name '*~' \
>>                -o -name '*.bak' -o -name '#*#' -o -name '.*.orig' \
>>                -o -name '.*.rej' -o -size 0 \
>>                -o -name '*%' -o -name '.*.cmd' -o -name 'core' \) \
>>                -type f -print | xargs rm -f
>>        $(call cmd,mrproper)
>>
> 
> 
> But dontdiff is a list of files that must be skipped, not a regex, right?
> Then dontdiff will be useless until a build has been done on that kernel tree.

Not really. From the diff manpage:

        -X FILE  --exclude-from=FILE
               Exclude files that match any pattern in FILE.

You may want to take a look at a copy of dontdiff (noting the shell 
patterns). It looks like dontdiff could be generated from mrproper's 
list of scratch files (with the exception of the '-size 0' test in the 
'find' command) but I could be wrong.

FWIW, the $(RCS_FIND_IGNORE) part skips some version-control directories 
that dontdiff doesn't mention. I guess the party line is that you should 
use the version control system for doing diffs in that case, but whatever.

If you try to replace dontdiff with a dynamically generated list, be 
sure and have a few folks test it out on different trees (including ones 
managed by BK and SVN) to make sure you haven't broken anything.

-C



  reply	other threads:[~2003-09-01 22:29 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 [this message]
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

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='bj0h8a$ev5$1@sea.gmane.org' \
    --to=clepple@ghz.cc \
    --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;
as well as URLs for NNTP newsgroup(s).