From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC - Moving categories around]
Date: Tue, 08 May 2007 23:11:09 -0700 [thread overview]
Message-ID: <464165FD.1050203@gentoo.org> (raw)
In-Reply-To: <b41005390705082304k688f6fddk7c61615e4eaa517f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Alec Warner wrote:
> The benefits include making the layout cleaner, obsoleting the
> categories file.
You talked a lot about how to do this, but I'd like to see you expand on
the reasoning for why. Balancing the breakage and extra work against the
reasons for making the change is hard to do without all the information.
Thanks,
Donnie
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-09 6:14 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 [this message]
2007-05-09 6:12 ` Ciaran McCreesh
2007-05-09 15:08 ` Piotr Jaroszyński
2007-05-09 19:29 ` [gentoo-dev] " Steve Long
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=464165FD.1050203@gentoo.org \
--to=dberkholz@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