From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev] [GLEP] GLEP Purpose and Guidelines
Date: Thu, 19 Jun 2008 17:54:12 +0400 [thread overview]
Message-ID: <1213883654.5167.87.camel@camobap> (raw)
In-Reply-To: <g37q7l$gmu$1@ger.gmane.org>
В Втр, 17/06/2008 в 09:48 +0200, Tiziano Müller пишет:
> http://dev.gentoo.org/~dev-zero/glep/glep-glep.txt
Your GLEP describes only two possible types: Technical and
Organizational. At the same time type of your GLEP is informational. How
this could be? What happens with informational GLEPs?
Why did you dropped motivation from the body while mentioning it in
workflow? What about previous copyright claim?
Actually this is just a beginning of questions and generally it feels
this glep is not finished and should borrow more ideas from the current
GLEP 1. It's even better to update GLEP 1 instead for writing new one...
--
Peter.
--
gentoo-project@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-19 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 7:48 [gentoo-project] [GLEP] GLEP Purpose and Guidelines Tiziano Müller
2008-06-19 13:54 ` Peter Volkov [this message]
2008-06-19 14:22 ` [gentoo-project] Re: [gentoo-dev] " Tiziano Müller
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=1213883654.5167.87.camel@camobap \
--to=pva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@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