public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Cory Visi <merlin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] development-sources are not 'development'
Date: Tue, 24 Aug 2004 01:35:30 +0000	[thread overview]
Message-ID: <20040824013530.GA23968@toucan.gentoo.org> (raw)
In-Reply-To: <412A9AFD.2030609@gentoo.org>

On Mon, Aug 23, 2004 at 09:33:49PM -0400, Travis Tilley wrote:
> if we must keep the 2.6 kernels seperate, i suggest that we at least 
> change the name of the package. it's incredibly confusing to have your 
> stable kernel named 'development-sources' or 'gentoo-dev-sources', and 
> there are archs like amd64 that just dont support 2.4 in any way. plus 
> with the new change in kernel development, mm-sources has become the 
> official development tree.
> 
> does anyone object to renaming development-sources to linux26-sources? 
> perhaps a similar name change for gentoo-dev-sources and 
> hardened-dev-sources?

I object to version numbers in the package name. I wasn't around for 
linux26-headers, so I won't dig up that discussion, but I object to this.

Thanks,
Cory

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-08-24  1:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  1:33 [gentoo-dev] development-sources are not 'development' Travis Tilley
2004-08-24  1:35 ` Cory Visi [this message]
2004-08-24  1:51 ` Mike Frysinger
2004-08-24  2:43 ` Peter Gordon
2004-08-24  3:15   ` Kumba
2004-08-24  3:32     ` Mike Frysinger
2004-08-24 13:20       ` Chris Gianelloni
2004-08-24  3:31   ` Mike Frysinger
2004-08-24  3:58     ` Peter Gordon
2004-08-24  4:04       ` Mike Frysinger
2004-08-24  5:38     ` Marius Mauch
2004-08-24 10:26   ` Travis Tilley
2004-08-24 13:26     ` Chris Gianelloni
2004-08-25 15:42       ` Cory Visi
2004-08-25 22:14         ` William Kenworthy
2004-08-27 20:54           ` Sven Vermeulen
2004-08-27 21:19             ` Sven Vermeulen

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=20040824013530.GA23968@toucan.gentoo.org \
    --to=merlin@gentoo.org \
    --cc=gentoo-dev@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