From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [Fwd: Re: [gentoo-trustees] joint copyright agreement]
Date: Tue, 20 Sep 2005 11:49:53 -0500 [thread overview]
Message-ID: <20050920164953.GF12282@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <1127226270.7845.25.camel@Memoria.anyarch.net>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
> From: Seemant Kulleen <seemant@gentoo.org>
> How does this agreement play to things like that? If eselect goes on
> (and based on its technical merits, there is every reason that it
> should) to become the default tool in gentoo, then where does that leave
> us? I'm with Grant on this: I'm not convinced.
Unsurprisingly, eselect was exactly what I was thinking about when I
raised that question.
-g2boojum-
--
Grant Goodyear
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-20 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 14:24 [Fwd: Re: [gentoo-trustees] joint copyright agreement] Daniel Ostrow
2005-09-20 16:49 ` Grant Goodyear [this message]
2005-09-20 16:57 ` Daniel Ostrow
2005-09-20 17:02 ` Daniel Ostrow
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=20050920164953.GF12282@bmb24.uth.tmc.edu \
--to=g2boojum@gentoo.org \
--cc=gentoo-trustees@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