From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org, chrisw@osdl.org
Subject: Re: Linux 2.6.11.1
Date: Sat, 5 Mar 2005 21:03:25 -0800 [thread overview]
Message-ID: <20050306050325.GA11889@kroah.com> (raw)
In-Reply-To: <42290D58.6090908@pobox.com>
On Fri, Mar 04, 2005 at 08:37:28PM -0500, Jeff Garzik wrote:
> Greg KH wrote:
> >On Fri, Mar 04, 2005 at 02:36:14PM -0800, Andrew Morton wrote:
> >
> >>But we end up with a cset in the permanent kernel history which simply
> >>should not have been there.
> >
> >
> >Is this really a big deal?
>
> If you are pushing linux-release to Linus/Andrew rapidly, quick fixes
> will land in linux-2.6 rapidly, and more invasive stuff will land only
> in linux-2.6 when the invasive stuff is ready to go. It even takes the
> pressure off pushing invasive stuff ASAP.
>
> Have you pushed linux-2.6.11.1 upstream yet? :)
Having Linus pull from the 2.6.x.y bk tree, will not work out. We
probably don't want the .1, .2, and so on tags in the tree, as well as
not all fixes in there will be proper for his tree (like the 2 currently
in 2.6.11.1.) The "real" fix will go into his tree through the proper
ways.
But I/we will be sure to pick out the stuff that should go there and
send them to him.
thanks,
greg k-h
next prev parent reply other threads:[~2005-03-06 5:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:53 Linux 2.6.11.1 Greg KH
2005-03-04 17:53 ` Greg KH
2005-03-04 20:34 ` Ian Pilcher
2005-03-04 22:29 ` Greg KH
2005-03-04 20:44 ` Andrew Morton
2005-03-04 20:58 ` Greg KH
2005-03-04 21:15 ` Andrew Morton
2005-03-04 21:43 ` Greg KH
2005-03-04 21:54 ` Andrew Morton
2005-03-04 22:08 ` Greg KH
2005-03-04 21:53 ` Linus Torvalds
2005-03-04 21:59 ` Andrew Morton
2005-03-04 22:05 ` Greg KH
2005-03-04 22:36 ` Andrew Morton
2005-03-05 0:06 ` Greg KH
2005-03-05 0:28 ` Linus Torvalds
2005-03-05 7:53 ` Dave Jones
2005-03-06 5:05 ` Greg KH
2005-03-05 1:37 ` Jeff Garzik
2005-03-06 5:03 ` Greg KH [this message]
2005-03-05 9:51 ` Russell King
2005-03-05 17:19 ` Jeff Garzik
2005-03-05 17:40 ` Linus Torvalds
2005-03-05 17:46 ` Russell King
2005-03-05 21:17 ` Linus Torvalds
2005-03-05 21:49 ` Gene Heskett
2005-03-05 22:06 ` Lee Revell
2005-03-05 23:26 ` Gene Heskett
2005-03-07 17:18 ` Alan Cox
2005-03-08 20:16 ` Lee Revell
2005-03-05 17:50 ` Jeff Garzik
2005-03-05 18:22 ` Randy.Dunlap
2005-03-05 0:24 ` Jeff Garzik
2005-03-04 21:15 ` Trond Myklebust
2005-03-04 21:33 ` Jeff Garzik
2005-03-04 21:51 ` Andrew Morton
2005-03-04 21:58 ` Jeff Garzik
2005-03-05 7:11 ` James Bourne
2005-03-08 22:07 ` Bill Davidsen
2005-03-08 22:41 ` Chris Wright
2005-03-04 21:50 ` Dave Jones
2005-03-04 23:35 ` Andries Brouwer
2005-03-04 20:48 ` Steven Rostedt
2005-03-04 20:53 ` Greg KH
2005-03-04 21:02 ` Steven Rostedt
2005-03-05 18:32 ` L. A. Walsh
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:28 Paolo
2005-03-04 19:55 ` Greg KH
2005-03-04 20:01 ` Paolo
2005-03-04 20:00 ` Jeff Garzik
2005-03-05 6:16 Shawn Starr
2005-03-06 5:06 ` Greg KH
2005-03-07 4:01 ` Shawn Starr
2005-03-07 3:58 ` Randy.Dunlap
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=20050306050325.GA11889@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=jgarzik@pobox.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