From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] How are we doing for 2004.3?
Date: Fri, 22 Oct 2004 14:27:27 -0400 [thread overview]
Message-ID: <1098469647.8234.7.camel@localhost> (raw)
In-Reply-To: <1098468747.8234.5.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Fri, 2004-10-22 at 14:12 -0400, Chris Gianelloni wrote:
> I know that most of you were waiting for catalyst 1.1.0 and genkernel
> 3.1.0, along with the snapshot. Well, it's all done now, so let me know
> how you all are doing?
>
> Is anybody not releasing? Does anyone need more time?
>
> We have pushed back the upload date to the 29th of October, so that
> gives about 9 days to get everything done.
Yes... me like math... math good...
It 7 days... and I'm a retard.
--
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-22 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 18:12 [gentoo-releng] How are we doing for 2004.3? Chris Gianelloni
2004-10-22 18:27 ` Chris Gianelloni [this message]
2004-10-22 18:27 ` Jeffrey Forman
2004-10-22 18:55 ` Pieter Van den Abeele
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=1098469647.8234.7.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@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