public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-rc1
Date: Tue, 24 Aug 2004 14:48:30 -0700	[thread overview]
Message-ID: <412BB7AE.7050804@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408240031560.17766@ppc970.osdl.org>

Linus Torvalds wrote:
> Ok,
>  tons of patches merged, with me being away for a week, and also the
> normal pent-up patch demand after any stable kernel. Special thanks as
> always to Andrew, who synced up 200+ patches (he's attributed in the
> sign-off lines, but not in the appended shortlog, so I just wanted to
> point that out).
> 
> Changes all over: arm, ppc, sparc, acpi, i2c, usb, fbcon, ntfs, xfs, nfs,
> cpufreq, agp, sata, network drivers - you name it. Most of the changes are
> fairly small, but there's a lot of them.
> 
> Administrative trivia, and one thing I agonized over: should I make the
> patches relative to 2.6.8 or 2.6.8.1? I decided that since there is
> nothing that says that a "basic bug-fix" releases for a previous release
> might not happen _after_ we've done a -rc release for the next version, I
> can't sanely do patches against a bugfix release.
> 
> Thus the 2.6.9-rc1 patch is against plain 2.6.8. If you have 2.6.8.1, you
> need to undo the .1 patch, and apply the big one. BK users and tar-balls 
> don't see that particular confusion, of course ;)
> 

The kernel.org scripts I am pretty sure will assume 2.6.9-rc1 are against 
2.6.8, not 2.6.8.1.

	-hpa

  parent reply	other threads:[~2004-08-24 21:51 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
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 [this message]
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=412BB7AE.7050804@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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