From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC - Moving categories around]
Date: Wed, 09 May 2007 20:29:31 +0100 [thread overview]
Message-ID: <f1t7k1$ljn$1@sea.gmane.org> (raw)
In-Reply-To: 200705091708.21686.peper@gentoo.org
Piotr Jaroszy?ski wrote:
> On Wednesday 09 of May 2007 08:04:44 Alec Warner wrote:
>> The new layout would be:
> I would reserve the breakage for something more useful. Not that I don't
> like the idea, just imho such a layout change alone is not worth it.
>
If you were to have such a wide-ranging change, what else would you do?
So far we have tidying up categories and:
> support for packages belonging to multiple categories, multiple names
>for a single package
I seem to recall there were some other tree-wide changes discussed in
#-portage, but tbh they went over my head.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-05-09 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b41005390705082109m18d456e8n1ff39b08e822e142@mail.gmail.com>
2007-05-09 6:04 ` [gentoo-dev] [RFC - Moving categories around] Alec Warner
2007-05-09 6:11 ` Donnie Berkholz
2007-05-09 6:12 ` Ciaran McCreesh
2007-05-09 15:08 ` Piotr Jaroszyński
2007-05-09 19:29 ` Steve Long [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='f1t7k1$ljn$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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