From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 42 news items
Date: Wed, 02 May 2007 20:37:04 -0700 [thread overview]
Message-ID: <463958E0.9040101@gentoo.org> (raw)
In-Reply-To: <20070502181301.703b3f38@maya>
Stephen Bennett wrote:
> Anyone have a reason why we can't start to put them in the tree?
> Portage support is, I'm told, coming in a month or so, and other
> package managers have supported glep42 for a while now. The format is
> well specified by the GLEP, so compatibility shouldn't be an issue.
>
> The one thing I can see needing to be decided first is an open question
> in the glep: do we want to put the news items straight into gentoo-x86,
> or a seperate repository that will be merged into the tree during the
> cvs->rsync process?
Uh, the glep says a separate repo, there is an svn news repo I had
created months ago when portage support was merged into trunk.
-Alec
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-05-03 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 17:13 [gentoo-dev] GLEP 42 news items Stephen Bennett
2007-05-02 21:23 ` Charlie Shepherd
2007-05-03 3:37 ` Alec Warner [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=463958E0.9040101@gentoo.org \
--to=antarus@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