From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebookmerge unmask and ebook-*.ebuilds remove
Date: Mon, 11 Jul 2005 14:58:51 +0200 [thread overview]
Message-ID: <1121086732.13669.5.camel@sponge.fungus> (raw)
In-Reply-To: <1121086426.26579.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Mon, 2005-07-11 at 14:53 +0200, José Alberto Suárez López wrote:
> after a week w/o bugs for ebookmerge i will unmask it and i will remove
> all the ebook-*.ebuilds if nobody say the secret word.... ;)
A week? Any particular reason not to follow policy and wait 30 days?
./Brix
--
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-11 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:53 [gentoo-dev] ebookmerge unmask and ebook-*.ebuilds remove José Alberto Suárez López
2005-07-11 12:58 ` Henrik Brix Andersen [this message]
2005-07-11 13:10 ` José Alberto Suárez López
2005-07-11 18:57 ` Henrik Brix Andersen
2005-07-11 22:12 ` José Alberto Suárez López
2005-07-11 19:16 ` Robert Paskowitz
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=1121086732.13669.5.camel@sponge.fungus \
--to=brix@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