From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] baselayout-1.11.14 stabilization
Date: Wed, 21 Dec 2005 07:49:37 -0500 [thread overview]
Message-ID: <1135169377.11036.2.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <20051220143602.GC18141@toucan.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Tue, 2005-12-20 at 14:36 +0000, Mike Frysinger wrote:
> since we have baselayout-1.12.x in ~arch, the new stable candidate
> (1.11.14) isnt getting much air time ... can people try upgrading to
> it and post any feedback they have with it ? it should mostly be a
> bugfix release over 1.11.13 since we arent doing any more real features
> for the 1.11.x branch ...
Does this preclude any bug fixes going into 1.11 that affect the
release? I have at least two that I would love to get resolved before
2006.0's release, and waiting for the eventual stabilization of 1.12
isn't exactly the best plan for this.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
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:[~2005-12-21 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 14:36 [gentoo-dev] baselayout-1.11.14 stabilization Mike Frysinger
2005-12-20 15:53 ` Jakub Moc
2005-12-21 18:15 ` Paul Varner
2006-01-03 15:32 ` Chris Gianelloni
2005-12-21 9:09 ` Matthias Langer
2005-12-21 12:49 ` Chris Gianelloni [this message]
2005-12-21 13:13 ` Roy Marples
2005-12-21 14:30 ` Chris Gianelloni
2005-12-21 14:45 ` Mike Frysinger
2005-12-21 15:54 ` Chris Gianelloni
2005-12-21 14:26 ` Mike Frysinger
2005-12-21 14:31 ` Chris Gianelloni
2006-01-13 8:08 ` Mike Frysinger
2006-01-13 16:39 ` Markus Rothe
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=1135169377.11036.2.camel@vertigo.twi-31o2.org \
--to=wolf31o2@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