From: Dave Airlie <airlied@gmail.com>
To: Grant Coady <grant_lkml@dodo.com.au>
Cc: Voluspa <lista1@telia.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: Linux v2.6.12-rc6
Date: Tue, 7 Jun 2005 17:44:00 +1000 [thread overview]
Message-ID: <21d7e997050607004411bfa36b@mail.gmail.com> (raw)
In-Reply-To: <2lhaa112u32htehrvnmqg6vh2kl8puesj8@4ax.com>
> On Tue, 7 Jun 2005 08:37:31 +0200, Voluspa <lista1@telia.com> wrote:
> >Ah, sorry about the noise... I've been away from kernel testing too
> >long. I patched a 2.6.11.11 tree without noticing all the rejects (this
> >new machine is fast). But from what I remember, it was decided to do
> >the -rc patches against the latest stable codebase, in this case .11
> >Shrug.
> I dunno what the change was, patch didn't apply cleanly to 2.6.11,
> (no idea if bad .bz2, finger trouble), so I download whole thing
> instead, now running on three x86 boxen.
It was explicitly stated by Linus way back 2.6.8.1 time that
subsequent patches are against the base of the previous release, so
-rcs are against 2.6.x not 2.6.x.y.. which all makes great sense if
development is happening in parallel... I'm not sure I've ever heard
anything else stated to oppose this, but apparently some people have..
Dave.
next prev parent reply other threads:[~2005-06-07 7:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 6:11 Linux v2.6.12-rc6 Voluspa
2005-06-07 6:18 ` Ingo Molnar
2005-06-07 6:37 ` Voluspa
2005-06-07 7:06 ` Grant Coady
2005-06-07 7:44 ` Dave Airlie [this message]
2005-06-07 8:45 ` Voluspa
2005-06-07 8:19 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 18:08 Linus Torvalds
2005-06-06 19:26 ` Pavel Machek
2005-06-06 19:54 ` Jeff Garzik
2005-06-06 20:05 ` Pavel Machek
2005-06-06 21:11 ` Linus Torvalds
2005-06-06 21:54 ` Bill Davidsen
2005-06-06 20:12 ` Linus Torvalds
2005-06-06 20:14 ` Pavel Machek
2005-06-06 21:13 ` Linus Torvalds
2005-06-06 21:18 ` Pavel Machek
2005-06-06 21:36 ` Linus Torvalds
2005-06-06 21:41 ` Pavel Machek
2005-06-06 21:53 ` Linus Torvalds
2005-06-06 21:57 ` Jesper Juhl
2005-06-06 22:07 ` Russell King
2005-06-07 9:11 ` Johannes Stezenbach
2005-06-08 11:15 ` Johannes Stezenbach
2005-06-08 11:23 ` Brice Goglin
2005-06-08 11:37 ` Johannes Stezenbach
2005-06-17 17:48 ` Bill Davidsen
2005-06-18 13:57 ` Johannes Stezenbach
2005-06-18 17:10 ` Johannes Stezenbach
2005-06-07 13:05 ` Erik Mouw
2005-06-07 15:28 ` Linus Torvalds
2005-06-07 17:11 ` Erik Mouw
2005-06-07 17:28 ` Linus Torvalds
2005-06-08 2:08 ` Paul Mackerras
2005-06-08 17:11 ` Linus Torvalds
2005-06-08 16:20 ` Nicolas Pitre
2005-06-07 18:47 ` Jean Delvare
2005-06-09 8:10 ` Greg KH
2005-06-09 15:52 ` Jean Delvare
2005-06-09 16:32 ` Greg KH
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=21d7e997050607004411bfa36b@mail.gmail.com \
--to=airlied@gmail.com \
--cc=ak@suse.de \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.com \
--cc=mingo@elte.hu \
/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