From: Dave Jones <davej@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Distinguishing releases from pre-rc snapshots
Date: Tue, 16 Oct 2007 23:01:49 -0400 [thread overview]
Message-ID: <20071017030149.GC3397@redhat.com> (raw)
In-Reply-To: <1192589117.3672.31.camel@dv>
On Tue, Oct 16, 2007 at 10:45:17PM -0400, Pavel Roskin wrote:
>
> On Tue, 2007-10-16 at 22:34 -0400, Dave Jones wrote:
> > On Tue, Oct 16, 2007 at 10:22:43PM -0400, Pavel Roskin wrote:
> >
> > > It would be nice to establish a rule to increment the version number
> > > immediately after the kernel release and have a suffix to indicate that
> > > it's a pre-rc version. "rc0" is my personal favorite.
> >
> > fwiw, rc0 is also what the Fedora kernel uses for versioning when we're
> > shipping pre-rc1 kernels.
>
> Thanks! I didn't think of the possibility of anyone distributing
> precompiled kernels from the "pre-rc" window, but if Fedora does it
> (hopefully for beta-testers only), it should be absolutely clear that
> it's not just a release with some minor fixes.
yeah, this is just in our 'development' pool (also known as 'rawhide')
Proper releases only ever get full point releases + -stable as updates.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-10-17 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 2:22 Distinguishing releases from pre-rc snapshots Pavel Roskin
2007-10-17 2:34 ` Dave Jones
2007-10-17 2:45 ` Pavel Roskin
2007-10-17 3:01 ` Dave Jones [this message]
2007-10-17 2:41 ` Rik van Riel
2007-10-17 3:17 ` Pavel Roskin
2007-10-17 6:02 ` Frans Pop
2007-10-17 12:59 ` Pavel Roskin
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=20071017030149.GC3397@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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