From: John Mylchreest <johnm@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] [ANNOUNCE] genpatches-2.6.16-2 release
Date: Wed, 29 Mar 2006 10:44:45 +0100 [thread overview]
Message-ID: <20060329094445.GA16917@getafix.willow.local> (raw)
In-Reply-To: <442A0EFB.1050500@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Tue, Mar 28, 2006 at 11:37:15PM -0500, Kumba <kumba@gentoo.org> wrote:
> Henrik Brix Andersen wrote:
> fwiw, I've got mips-sources modified to follow the upstream kernel.org
> notation of 2.6.x.y (even though our primary upstream, linux-mips.org,
> doesn't utilize this notation at all).
>
> There's logic in the ebuild that can switch between using -rc, point
> releases (the .y ones) and standard versions, and it modifies the logic to
> fetch the appropriate patch(es) from upstream to save on what we need to
> upload to the gentoo mirrors.
>
> Been following this since ~2.6.12, and we haven't had any issues with the
> versioning in portage or reported from users. mips-headers even uses it
> now.
On that note, whats the chances of getting mips-sources/headers to use
kernel-2? ALl the logic exists already in there anyways (has done for
ages) and it would reduce that 500 odd line ebuild down to ~50 :)
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-03-29 9:44 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
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 [this message]
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=20060329094445.GA16917@getafix.willow.local \
--to=johnm@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