From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Alvaro Figueroa Cabezas <fede2@fuerzag.ulatina.ac.cr>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Where to put prerelease vanilla kernels?
Date: 23 Jul 2003 18:35:11 -0400 [thread overview]
Message-ID: <1058999711.3578.24.camel@vertigo> (raw)
In-Reply-To: <20030723082823.GP19204@fuerzag.ulatina.ac.cr>
Absolutely not. The policy is the correct method for numbering
versions. Your original understanding of how the policy used versions,
and how the kernel developers is incorrect. You could consider the
2.4.22_pre kernels as 2.4.21_p kernels... they are patches on top of
2.4.21 that will someday in the future become 2.4.22, therefore they're
newer. The portage policy is exactly in line with this.
On Wed, 2003-07-23 at 04:28, Alvaro Figueroa Cabezas wrote:
> Ohh I see. Shouldn't the policy be changed to make it the way I
> missunderstood it? I really don't see the why in the way it is.
--
Chris Gianelloni
Developer, Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-23 22:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 16:16 [gentoo-dev] Where to put prerelease vanilla kernels? Matt Rickard
2003-07-23 7:10 ` Alvaro Figueroa Cabezas
2003-07-23 19:16 ` Chris Gianelloni
2003-07-23 7:46 ` Alvaro Figueroa Cabezas
2003-07-23 20:03 ` donnie berkholz
2003-07-23 8:28 ` Alvaro Figueroa Cabezas
2003-07-23 20:51 ` Peter Johanson
2003-07-23 22:35 ` Chris Gianelloni [this message]
2003-07-23 19:21 ` donnie berkholz
2003-07-23 17:45 ` Jay Pfeifer
2003-07-23 19:39 ` Matt Rickard
2003-07-23 18:06 ` Dhruba Bandopadhyay
2003-07-23 18:24 ` Jay Pfeifer
2003-07-24 8:28 ` Sven Vermeulen
2003-07-24 9:07 ` Georgi Georgiev
2003-07-24 13:07 ` Matt Rickard
2003-07-24 13:38 ` Paul de Vrieze
2003-07-24 14:13 ` Terje Kvernes
2003-07-24 12:56 ` Matt Rickard
2003-07-24 13:49 ` Thomas de Grenier de Latour
2003-07-24 13:54 ` Thomas de Grenier de Latour
2003-08-25 17:43 ` Alvaro Figueroa
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=1058999711.3578.24.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=fede2@fuerzag.ulatina.ac.cr \
--cc=gentoo-dev@gentoo.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