From: Jason Huebel <jhuebel@gentoo.org>
To: gentoo-core@lists.gentoo.org
Cc: amd64@gentoo.org, gentoo-amd64@lists.gentoo.org,
gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] Re: [gentoo-core] Reminder: 2004.3 - Portage snapshot
Date: Thu, 14 Oct 2004 19:39:38 -0500 [thread overview]
Message-ID: <200410141939.44472.jhuebel@gentoo.org> (raw)
In-Reply-To: <20041007114606.GA1227@vega.hausnetz>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Thursday 07 October 2004 6:46 am, Benjamin Judas wrote:
> This is just a reminder that I will create the x86 snapshot on Oct. 16th.
> If you want to have anything stable in the release, YOU HAVE TO HAVE IT
> DONE BY THAT DATE. After that date, ONLY IMPORTANT security fixes will be
> included.
amd64 also has a drop-dead date of October 16th for our portage snapshot.
Expect that snapshot to be made tomorrow during the day sometime. Probably
around 1800UTC. A few hours thereafter, new stages and a new bare-bones
LiveCD should become available for testing. Over the weekend and next week,
the package and universal CDs will be built for amd64.
Is portage-2.0.51 going to be ready for tomorrow?
--
Jason Huebel
Gentoo/amd64 Strategic Lead
Gentoo Developer Relations/Recruiter
GPG Public Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230
"Do not weep; do not wax indignant. Understand."
Baruch Spinoza (1632 - 1677)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-10-15 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1096303376.12201.5.camel@antares.hausnetz>
[not found] ` <20041007114606.GA1227@vega.hausnetz>
2004-10-15 0:39 ` Jason Huebel [this message]
[not found] ` <20041015010811.GA7248@twobit.net>
2004-10-15 2:05 ` [gentoo-releng] Re: [gentoo-core] Reminder: 2004.3 - Portage snapshot Jason Huebel
2004-10-15 17:22 ` Benjamin Judas
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=200410141939.44472.jhuebel@gentoo.org \
--to=jhuebel@gentoo.org \
--cc=amd64@gentoo.org \
--cc=gentoo-amd64@lists.gentoo.org \
--cc=gentoo-core@lists.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