From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] help with GLEP 15
Date: Sun, 11 Jan 2004 19:49:35 -0600 [thread overview]
Message-ID: <200401111949.35361.iggy@gentoo.org> (raw)
In-Reply-To: <878ykegej4.fsf@jbms.ath.cx>
On Sunday 11 January 2004 07:07 pm, Jeremy Maitin-Shepard wrote:
> Brian Jackson <iggy@gentoo.org> writes:
> > For anyone who hasn't read it, GLEP 15's goal is to create a script
> > repository for developers and users to store useful scripts.
> >
> > [snip]
>
> Does not the gentoo-src module in the CVS repository serve this purpose,
> at least for developers?
Sure it serves the purposes of storage, but it's not standardized, and there's
no interaction like we have planned for the script repository. It also makes
it harder for users to contribute which is something we don't need more of.
There are numerous other reasons why a nicely done repository will be loads
better than cvs.
--Iggy
--
Home -- http://www.brianandsara.net
Gentoo -- http://gentoo.brianandsara.net
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-12 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 0:26 [gentoo-dev] help with GLEP 15 Brian Jackson
2004-01-12 1:07 ` Jeremy Maitin-Shepard
2004-01-12 1:49 ` Brian Jackson [this message]
2004-01-12 10:53 ` Ian Leitch
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=200401111949.35361.iggy@gentoo.org \
--to=iggy@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