All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Matt Mackall <mpm@selenic.com>, Bill Davidsen <davidsen@tmr.com>,
	Pavel Machek <pavel@ucw.cz>,
	"Marcos D. Marado Torres" <marado@student.dei.uc.pt>,
	linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: Linux 2.6.11.2
Date: Fri, 11 Mar 2005 14:01:50 -0800	[thread overview]
Message-ID: <20050311220150.GA4925@kroah.com> (raw)
In-Reply-To: <20050311191928.GK5389@shell0.pdx.osdl.net>

On Fri, Mar 11, 2005 at 11:19:28AM -0800, Chris Wright wrote:
> * Matt Mackall (mpm@selenic.com) wrote:
> > Or do you want to do it the same way you do for every other branch? I
> > don't want to special-case it in my code and I don't think users want
> > to special-case it in their brains. Have separate interdiffs on the
> > side, please, and then people can choose, but do it the standard way.
> > 
> > Dear ${SUCKER}s, can we have a decision on this? My ketchup tool is
> > broken for 2.6.11.2 and I don't want to cut a new release until a firm
> > decision is made. Obviously I have a strong preference for all 2.6.x.y
> > diffs being against 2.6.x, it means that .y can be treated the same as
> > -rc, -bk, -mm, ... (and I already coded it that way when 2.6.8.1 came
> > out).
> 
> I agree with having the patch be against .x, with x.y -> x.y+1 interdiffs
> available on the side.  Greg, any issue with that?

No, I agree with that, and will not be hard to do at all (the release
script already handles this just fine.)  

I've held off rediffing 2.6.11.2 so far, as I don't know where to put
the x.y+1 interdiffs?  kernel/v2.6/incr/ ?  Any thoughts?

thanks,

greg k-h

  reply	other threads:[~2005-03-11 22:45 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 [this message]
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
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=20050311220150.GA4925@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    --cc=mpm@selenic.com \
    --cc=pavel@ucw.cz \
    --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.