From: Tigran Aivazian <tigran@veritas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, <tigran@aivazian.fsnet.co.uk>
Subject: Re: dontdiff for 2.6.0-test4
Date: Mon, 1 Sep 2003 08:51:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.44.0309010848040.18476-100000@north.veritas.com> (raw)
In-Reply-To: <20030901163958.A24464@infradead.org>
> On Mon, Sep 01, 2003 at 07:57:27AM -0700, Tigran Aivazian wrote:
> > I have updated dontdiff in the usual place:
> >
> > http://www.moses.uklinux.net/patches/dontdiff
> >
> > for the 2.6 kernels. Obviously this was only tested on my configuration(s)
> > so any additions are welcome. Just email them to me and I will add them.
> >
> > For those who don't know what "dontdiff" is --- grep the file:
> >
> > /usr/src/linux/Documentation/SubmittingPatches
>
> Btw, what about putting this somewhere in the kernel tree?
Probably a good idea, because I hesitated whether to call this
"dontdiff-2.6" and leave the existing dontdiff for 2.4 or just switch to
2.6 (assuming it is applicable to 2.4 as well). But if it is in the kernel
tree then no need to worry about which dontdiff matches which kernel.
Regards
Tigran
next prev parent reply other threads:[~2003-09-01 15:52 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 [this message]
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
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=Pine.GSO.4.44.0309010848040.18476-100000@north.veritas.com \
--to=tigran@veritas.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@aivazian.fsnet.co.uk \
/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®