From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 43: GLEP File Hosting
Date: Fri, 11 Nov 2005 15:47:06 +0100 [thread overview]
Message-ID: <200511111547.06908.pauldv@gentoo.org> (raw)
In-Reply-To: <20051107215613.1e895d72@snowdrop.home>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Monday 07 November 2005 22:56, Ciaran McCreesh wrote:
> Ok, this is a change to the GLEP process, so it itself needs to be a
> GLEP... All it does is propose that GLEPs be allowed to stick example
> code in a subdirectory rather than having to inline things or shove
> them off on someone's devspace.
>
> Text version attached. An HTML version will be up on the main site
> whenever the web nodes next sync -- may be wise to read that instead if
> you aren't familiar with RST :: blocks.
I see no objections to this.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2005-11-11 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 21:56 [gentoo-dev] GLEP 43: GLEP File Hosting Ciaran McCreesh
2005-11-08 0:34 ` Dan Meltzer
2005-11-08 0:41 ` Ciaran McCreesh
2005-11-08 0:45 ` Dan Meltzer
2005-11-11 14:47 ` Paul de Vrieze [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=200511111547.06908.pauldv@gentoo.org \
--to=pauldv@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