From: Brian Harring <ferringb@gmail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Petteri RRRty <betelgeuse@gentoo.org>,
council@gentoo.org, gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] Re: EAPI 4 approval
Date: Wed, 29 Dec 2010 04:07:27 -0800 [thread overview]
Message-ID: <20101229120727.GB12162@hrair> (raw)
In-Reply-To: <19738.61438.451956.311867@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Wed, Dec 29, 2010 at 09:23:26AM +0100, Ulrich Mueller wrote:
> >>>>> On Tue, 28 Dec 2010, Ulrich Mueller wrote:
>
> > So unless there are any last-minute changes (Fauli?), the following
> > commit should be tagged:
>
> There's another trivial update (removal of an unused file, output is
> not affected), so the commit to be tagged is:
> <http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=348ea6c695bf7fe079c43e294ddbd06bca3d0cfc>
+1 on 348ea6c695bf7fe079c43e294ddbd06bca3d0cfc as the tagging point.
> > The tag should be called "eapi-4-approved-2010-12-30" if we follow the
> > convention we used for EAPIs 2 and 3.
I'm personally of the opinion that should just be "eapi-4"; the commit
msg can include the approval specifics.
If we need to approve a tweaked version of eapi4 itself- just name it
"eapi-4-v1" or whatever. Jamming the approval date in is annoying
however.
~brian
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-29 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D145D72.2040100@gentoo.org>
[not found] ` <19732.29261.835025.991984@a1i15.kph.uni-mainz.de>
[not found] ` <4D147827.9000404@gentoo.org>
2010-12-24 11:34 ` [gentoo-pms] Re: EAPI 4 approval Christian Faulhammer
2010-12-28 8:07 ` Ulrich Mueller
2010-12-29 8:23 ` Ulrich Mueller
2010-12-29 12:07 ` Brian Harring [this message]
[not found] ` <20101229225039.GA21534@linuxized.com>
[not found] ` <4D1BBCFA.9060107@gentoo.org>
2010-12-29 23:06 ` Mark Loeser
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=20101229120727.GB12162@hrair \
--to=ferringb@gmail.com \
--cc=betelgeuse@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-pms@lists.gentoo.org \
--cc=ulm@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