linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Ted Ts'o <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org, DRI <dri-devel@lists.freedesktop.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@suse.de>
Subject: Re: (Short?) merge window reminder
Date: Mon, 23 May 2011 16:21:43 -0700	[thread overview]
Message-ID: <20110523162143.fdf2f2a7.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110523231721.GM10009@thunk.org>

On Mon, 23 May 2011 19:17:21 -0400 Ted Ts'o wrote:

> On Mon, May 23, 2011 at 01:33:48PM -0700, Linus Torvalds wrote:
> > On Mon, May 23, 2011 at 12:20 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > I really hope there's also a voice that tells you to wait until .42 before
> > > cutting 3.0.0! :-)
> > 
> > So I'm toying with 3.0 (and in that case, it really would be "3.0",
> > not "3.0.0" - the stable team would get the third digit rather than
> > the fourth one.
> 
> If we change from 2.6.X to 3.X, then if we don't change anything else,
> then successive stable release will cause the LINUX_VERSION_CODE to be
> incremented.  This isn't necessary bad, but it would be a different
> from what we have now.


It's just another little thing to break several scripts...


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-05-23 23:21 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 19:13 (Short?) merge window reminder Linus Torvalds
2011-05-23 19:20 ` Ingo Molnar
2011-05-23 20:33   ` Linus Torvalds
2011-05-23 20:52     ` Alexey Zaytsev
2011-05-25 14:12       ` Boaz Harrosh
2011-05-25 22:21         ` Tony Luck
2011-05-26 16:38           ` Boaz Harrosh
2011-05-23 21:59     ` Oliver Pinter
2011-05-23 22:21     ` Greg KH
2011-05-23 23:40       ` Matthew Wilcox
2011-05-23 23:10     ` jonsmirl
2011-05-23 23:17     ` Ted Ts'o
2011-05-23 23:21       ` Randy Dunlap [this message]
2011-05-23 23:23       ` H. Peter Anvin
     [not found]       ` <4DDAEC68.30803@zytor.com>
2011-05-23 23:33         ` Linus Torvalds
2011-05-24  2:01           ` Ingo Molnar
2011-05-24  7:55           ` Arnd Bergmann
2011-05-24 12:15           ` Jan Engelhardt
2011-05-24 12:30             ` Jacek Luczak
2011-05-24 13:02               ` Jan Engelhardt
2011-05-24 13:18                 ` Jacek Luczak
2011-05-24 14:43                   ` Alan Cox
2011-05-24 15:07                     ` jonsmirl
2011-05-24 17:36                       ` H. Peter Anvin
2011-05-24 17:41                         ` Linus Torvalds
2011-05-24 18:48                           ` eschvoca
2011-05-24 21:05                             ` Jan Engelhardt
2011-05-25  9:12                               ` Emil Langrock
2011-05-26 16:13                       ` Sérgio Basto
2011-05-27  9:20                         ` Lukasz
2011-05-24 15:46                     ` Ralf Baechle
2011-05-24 17:29                       ` Jan Engelhardt
2011-05-25  1:13               ` Valdis.Kletnieks
2011-05-24 14:41       ` Alan Cox
2011-05-24 14:48       ` Ralf Baechle
2011-05-23 23:53     ` Phil Turmel
2011-05-24  2:11     ` Ingo Molnar
2011-05-24 18:06     ` Lisa Milne
2011-05-24 20:59       ` Zimny Lech
2011-05-25 15:03         ` Martin Nybo Andersen
2011-05-24 18:34     ` Matthias Schniedermeyer
2011-05-24 18:55       ` david
2011-05-24 21:25     ` Andy Lutomirski
2011-05-25 12:52       ` Jiri Kosina
2011-05-24 23:00     ` Hans-Peter Jansen
2011-05-23 19:22 ` Greg KH
2011-05-23 20:04   ` James Bottomley
2011-05-23 19:25 ` Thomas Gleixner
2011-05-23 20:21   ` Randy Dunlap
2011-05-23 21:02     ` Steven Rostedt
2011-05-24 19:06 ` Emil Langrock

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=20110523162143.fdf2f2a7.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@suse.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).