From: Daniel Drake <dsd@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] [ANNOUNCE] genpatches-2.6.16-2 release
Date: Tue, 28 Mar 2006 17:48:13 +0100 [thread overview]
Message-ID: <442968CD.2030208@gentoo.org> (raw)
In-Reply-To: <20060328132657.GE17806@getafix.willow.local>
John Mylchreest wrote:
> On Tue, Mar 28, 2006 at 02:19:22PM +0100, Daniel Drake <dsd@gentoo.org> wrote:
>> Revision 347:
>> Linux 2.6.16.1 thanks to Francisco Lloret in bug #127838 (dsd)
>> Added: 1000_linux-2.6.16.1.patch
>
> Since were bunlding these whole now, should we just start naming the
> ebuilds correctly instead?
I don't think so. 2 -stable releases in the 2.6.15 cycle didn't have any
immediate corresponding gentoo-sources bump since the patches were
already included. The fact that we include patches alongside -stable
means that using their notation isn't entirely accurate in our situation.
Daniel
--
gentoo-kernel@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-28 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 13:19 [gentoo-kernel] [ANNOUNCE] genpatches-2.6.16-2 release Daniel Drake
2006-03-28 13:26 ` John Mylchreest
2006-03-28 16:48 ` Daniel Drake [this message]
2006-03-28 17:09 ` Henrik Brix Andersen
2006-03-29 4:37 ` Kumba
2006-03-29 6:59 ` Henrik Brix Andersen
2006-03-29 9:44 ` John Mylchreest
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=442968CD.2030208@gentoo.org \
--to=dsd@gentoo.org \
--cc=gentoo-kernel@lists.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