From: "Charlie Shepherd" <masterdriverz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 42 news items
Date: Wed, 2 May 2007 22:23:28 +0100 [thread overview]
Message-ID: <fc8ec2a10705021423n332bd305j61291ab03000e347@mail.gmail.com> (raw)
In-Reply-To: <20070502181301.703b3f38@maya>
On 02/05/07, Stephen Bennett <spb@gentoo.org> wrote:
> 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?
>From reading the glep it's always been my impression that the latter
would be the case:
"The contents of this repository will automatically be merged with the
main rsync tree, placing the items in a metadata/news/ directory."
--
-Charlie
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-02 21:26 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 [this message]
2007-05-03 3:37 ` Alec Warner
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=fc8ec2a10705021423n332bd305j61291ab03000e347@mail.gmail.com \
--to=masterdriverz@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