From: Florian Weimer <fw@deneb.enyo.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-rc1
Date: Tue, 24 Aug 2004 21:54:33 +0200 [thread overview]
Message-ID: <871xhwb9c6.fsf@deneb.enyo.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408241221390.17766@ppc970.osdl.org> (Linus Torvalds's message of "Tue, 24 Aug 2004 12:23:42 -0700 (PDT)")
* Linus Torvalds:
> On Tue, 24 Aug 2004, Matt Mackall wrote:
>>
>> Phew, I was worried about that. Can I get a ruling on how you intend
>> to handle a x.y.z.1 to x.y.z.2 transition? I've got a tool that I'm
>> looking to unbreak. My preference would be for all x.y.z.n patches to
>> be relative to x.y.z.
>
> Hmm.. I have no strong preferences. There _is_ obviously a well-defined
> ordering from x.y.z.1 -> x.y.z.2 (unlike the -rcX releases that don't have
> any ordering wrt the bugfixes), so either interdiffs or whole new full
> diffs are totally "logical". We just have to chose one way or the other,
> and I don't actually much care.
It would be slightly more consistent to diff .2 against .1 because
this is what already happens when a new x.y.z release is published.
next prev parent reply other threads:[~2004-08-24 19:54 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 7:49 Linux 2.6.9-rc1 Linus Torvalds
2004-08-24 16:40 ` Linux 2.6.9-rc1 (compile stats) John Cherry
2004-08-24 16:41 ` Linux 2.6.9-rc1 Pierre Ossman
2004-08-24 16:46 ` Russell King
2004-08-24 16:59 ` Pierre Ossman
2004-08-24 17:50 ` Alexander Gran
2004-08-24 18:42 ` Matt Mackall
2004-08-24 19:23 ` Linus Torvalds
2004-08-24 19:38 ` Chris Meadors
2004-08-24 19:54 ` Florian Weimer [this message]
2004-08-24 20:13 ` Josh Boyer
2004-08-24 20:25 ` Jesper Juhl
2004-08-24 20:07 ` Tim Schmielau
2004-08-24 20:32 ` Matt Mackall
2004-08-24 21:22 ` Martin J. Bligh
2004-08-24 22:55 ` Dave Hansen
2004-08-24 22:52 ` H. Peter Anvin
2004-08-24 23:46 ` Dâniel Fraga
2004-08-25 0:11 ` Daniel Andersen
2004-08-25 1:01 ` Dâniel Fraga
2004-08-25 4:24 ` H. Peter Anvin
2004-08-25 20:36 ` Bill Davidsen
2004-08-25 0:25 ` Stephen Wille Padnos
2004-08-25 1:11 ` Dâniel Fraga
2004-08-25 9:13 ` Geert Uytterhoeven
2004-08-25 20:18 ` Bill Davidsen
2004-08-24 18:54 ` Chris Wedgwood
2004-08-24 21:48 ` H. Peter Anvin
2004-08-24 21:58 ` Randy.Dunlap
2004-08-25 14:45 ` Chris Friesen
2004-08-25 16:12 ` Matthias Andree
2004-08-25 18:52 ` Joshua Kwan
2004-08-25 20:32 ` Harald Welte
2004-08-25 21:35 ` Henrik Nordstrom
2004-08-25 23:48 ` Harald Welte
2004-08-25 23:44 ` David S. Miller
2004-08-26 3:14 ` Joshua Kwan
2004-08-26 8:02 ` Harald Welte
2004-08-26 5:07 ` Mark Lord
[not found] ` <20040825231407.058b3ea6.davem@redhat.com>
2004-08-26 6:15 ` David S. Miller
2004-08-31 17:34 ` 2.6.9-rc1: missing netfilter help texts Adrian Bunk
2004-08-31 18:40 ` [netfilter-core] " Harald Welte
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 0:31 Linux 2.6.9-rc1 Sartorelli, Kevin
2004-08-25 1:05 ` Daniel Andersen
2004-08-25 1:20 ` Linus Torvalds
2004-08-25 14:52 ` Martin J. Bligh
2004-08-25 21:14 ` Roman Zippel
2004-08-26 8:09 ` Denis Vlasenko
2004-08-26 8:35 ` Geert Uytterhoeven
2004-08-27 12:45 ` Horst von Brand
2004-08-27 21:30 ` Denis Vlasenko
2004-08-25 20:27 ` Bill Davidsen
2004-08-25 22:20 David Mansfield
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=871xhwb9c6.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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