All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alastair Stevens <alastair@altrux.me.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: From 2.4 to 2.6 to 2.7?
Date: Thu, 17 Jul 2008 23:05:07 +0100	[thread overview]
Message-ID: <487FC213.9030604@altrux.me.uk> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Forgive me if I missed it, but I've not seen any suggestions along the lines
of this: how about just dropping the now-meaningless '.6' from the version
string and retaining the rest. In other words:

   2.27
   2.27.1
   ...
   2.28
   2.28.1
   2.28.2

That way you continue the series in a meaningful way, whilst reverting to a
neater 3-level numbering scheme again. Perhaps you could make 2.[6.]30 the
switchover point....

Cheers
AL

- --
====================================================================
ALASTAIR STEVENS
* Web - www.altrux.me.uk
* Blog - www.altrux.me.uk/blog.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIf8ITxW64B3bJb+wRAlxMAJ0cRiRBeN2MVBxauLudZDBQ9mEjEACfVx0C
kNjXCycMZ+rxLvoMIVh0EAY=
=04yz
-----END PGP SIGNATURE-----

             reply	other threads:[~2008-07-17 22:05 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 22:05 Alastair Stevens [this message]
2008-07-17 22:40 ` From 2.4 to 2.6 to 2.7? Lennart Sorensen
2008-07-18  8:23   ` Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
2008-07-15  2:10 Stoyan Gaydarov
2008-07-15  2:22 ` Linus Torvalds
2008-07-15  2:31   ` Stoyan Gaydarov
2008-07-15  2:47     ` Linus Torvalds
2008-07-15  3:55       ` david
2008-07-15  5:31         ` Willy Tarreau
2008-07-15  6:40           ` Rafael C. de Almeida
2008-07-15  7:23           ` Stoyan Gaydarov
2008-07-15  7:49       ` Jan Engelhardt
2008-07-17 17:25         ` Jan Engelhardt
2008-07-17 19:56           ` Craig Milo Rogers
2008-07-17 20:21             ` Jan Engelhardt
2008-07-19  8:00               ` Craig Milo Rogers
2008-07-19  8:52                 ` Rene Herman
2008-07-19 20:49                   ` Craig Milo Rogers
2008-07-19 20:56                     ` david
2008-07-19 21:56                       ` Jan Engelhardt
2008-07-20  8:34                     ` Rene Herman
2008-07-20 14:53                       ` Stefanos Harhalakis
2008-07-19 19:30                 ` Peter T. Breuer
2008-07-19 21:16                   ` Craig Milo Rogers
2008-07-19 23:10                     ` Peter T. Breuer
2008-07-15  8:29       ` Bernd Petrovitsch
2008-07-15 12:41       ` Kasper Sandberg
2008-07-15 13:18         ` Alberto Gonzalez
2008-07-15 18:06       ` Charles grey wolf Banas
2008-07-15 20:43       ` Adrian Bunk
2008-07-16  7:53         ` Jan Engelhardt
2008-07-16  7:57           ` Rene Herman
2008-07-17 22:16         ` Adrian Bunk
2008-07-15 10:10   ` Andi Kleen
2008-07-15 11:31     ` Jan Engelhardt
2008-07-15 15:20     ` Linus Torvalds
2008-07-15 15:27     ` Parag Warudkar
2008-07-15 15:32       ` Alan Cox
2008-07-18  9:02         ` Andi Kleen
2008-07-16 21:11     ` Lennart Sorensen
2008-07-15 12:38   ` Alan Cox
2008-07-15 14:07   ` Byron Stanoszek
2008-07-16 21:14     ` Lennart Sorensen
2008-07-17  0:03       ` Alex Chiang
2008-07-17 12:38         ` Lennart Sorensen
2008-07-17 20:02           ` Alex Chiang
2008-07-15 14:24   ` Cyrill Gorcunov
2008-07-15 16:36     ` Tobias Brox
2008-07-15 18:04   ` H. Peter Anvin
2008-07-16  4:22     ` Rene Herman
2008-07-16  6:55       ` Rafael C. de Almeida
2008-07-16  7:17         ` Rene Herman
2008-07-16  7:30         ` Rene Herman
2008-07-16  9:34       ` Peter T. Breuer

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=487FC213.9030604@altrux.me.uk \
    --to=alastair@altrux.me.uk \
    --cc=linux-kernel@vger.kernel.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.