All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, chrisw@osdl.org, torvalds@osdl.org,
	akpm@osdl.org
Subject: Re: Linux 2.6.11.2
Date: Wed, 9 Mar 2005 15:38:07 -0800	[thread overview]
Message-ID: <20050309233807.GF3120@waste.org> (raw)
In-Reply-To: <20050309231156.GB31064@kroah.com>

On Wed, Mar 09, 2005 at 03:11:57PM -0800, Greg KH wrote:
> On Wed, Mar 09, 2005 at 01:06:31PM -0800, Matt Mackall wrote:
> > On Wed, Mar 09, 2005 at 12:39:23AM -0800, Greg KH wrote:
> > > And to further test this whole -stable system, I've released 2.6.11.2.
> > > It contains one patch, which is already in the -bk tree, and came from
> > > the security team (hence the lack of the longer review cycle).
> > > 
> > > It's available now in the normal kernel.org places:
> > > 	kernel.org/pub/linux/kernel/v2.6/patch-2.6.11.2.gz
> > > which is a patch against the 2.6.11.1 release.
> > 
> > Argh! @*#$&!!&! 
> > 
> > > If consensus arrives
> > > that this patch should be against the 2.6.11 tree, it will be done that
> > > way in the future.
> > 
> > Consensus arrived back when 2.6.8.1 came out.
> 
> It did?  So, what was it agreed to be?  Any pointers to that agreement?

Deltas against 2.6.x tarballs. The discussion was some large fraction
of the 2.6.8.1 announce thread. I think someone else mentioned it in
the recent renumbering thread, so I didn't feel the need to
pre-emptively whinge this time around..

> > Fixing it in the future is too #*$%* late because you've now turned it
> > into a special case.
> 
> No, I can always respin the patch, and re-release it if it's a problem.

That'd make things easier, yes.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2005-03-09 23:40 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  8:39 Linux 2.6.11.2 Greg KH
2005-03-09  8:39 ` Greg KH
2005-03-17 15:18   ` Gene Heskett
2005-03-09  9:52 ` Marcos D. Marado Torres
2005-03-09 10:04   ` Geert Uytterhoeven
2005-03-09 10:17     ` Marcos D. Marado Torres
2005-03-09 10:41       ` Geert Uytterhoeven
2005-03-09 11:23         ` Jesper Juhl
2005-03-09 21:26       ` Wakko Warner
2005-03-09 10:21     ` Dominik Karall
2005-03-09 10:28       ` Marcos D. Marado Torres
2005-03-09 10:51         ` Adrian Bunk
2005-03-09 15:35         ` Greg KH
2005-03-09 11:11   ` Pavel Machek
2005-03-09 23:57     ` Matt Mackall
2005-03-10  5:16       ` Willy Tarreau
2005-03-11 18:45       ` Bill Davidsen
2005-03-11 19:08         ` Matt Mackall
2005-03-11 19:19           ` Chris Wright
2005-03-11 22:01             ` Greg KH
2005-03-14 17:10               ` Bill Davidsen
2005-03-14 17:32                 ` Greg KH
2005-03-15 20:38           ` Bill Davidsen
2005-03-16  8:56             ` David Greaves
2005-03-09 12:38 ` Andy Whitcroft
2005-03-09 14:03 ` Marcelo Tosatti
2005-03-09 18:38   ` Greg KH
2005-03-09 20:32 ` Bill Davidsen
2005-03-09 21:06 ` Matt Mackall
2005-03-09 21:21   ` Randy.Dunlap
2005-03-09 23:11   ` Greg KH
2005-03-09 23:38     ` Matt Mackall [this message]
2005-03-10 12:54     ` Gene Heskett
2005-03-11 19:23       ` Bill Davidsen
2005-03-11 23:33         ` Gene Heskett
2005-03-11 14:53 ` Krzysztof Halasa
2005-03-11 17:38   ` Chris Wright
2005-03-11 19:28     ` Bill Davidsen
2005-03-11 21:07     ` Krzysztof Halasa
2005-03-11 21:11       ` Chris Wright
     [not found] <fa.dan38um.1m4gojq@ifi.uio.no>
     [not found] ` <fa.animhpl.r201hh@ifi.uio.no>
2005-03-10  1:46   ` Bodo Eggert
2005-03-10  3:08     ` Matt Mackall

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=20050309233807.GF3120@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.