public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: bash version in ebuilds/eclasses...non-compliance and what to do?
Date: Sat, 20 Dec 2008 13:54:44 +0000	[thread overview]
Message-ID: <20081220135444.03efc830@snowmobile> (raw)
In-Reply-To: <gii0m0$e8f$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]

On Sat, 20 Dec 2008 05:35:25 +0000
Steve Long <slong@rathaus.eclipse.co.uk> wrote:
> I note that bash-3.2_p17-r1 is stable on all the architectures that
> 3.0-r12 lists (it just adds the two -fbsd archs as unstable.)
> portage-2.1.4.5 requires at least that version (only unstable on mips
> as against 2.1.1-r2) It might be worth skipping to 3.2, since that
> would simplify regex handling.

Stable isn't the measure. Stages are. Read the original email carefully
and you shall see why.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-12-20 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 23:46 [gentoo-dev] bash version in ebuilds/eclasses...non-compliance and what to do? Jeremy Olexa
2008-12-20  5:35 ` [gentoo-dev] " Steve Long
2008-12-20  9:42   ` Fabian Groffen
2008-12-24 11:31     ` [gentoo-dev] " Steve Long
2008-12-20 13:54   ` Ciaran McCreesh [this message]
2010-01-15  5:34 ` [gentoo-dev] " Mike Frysinger
2010-01-15 10:46   ` Fabian Groffen
2010-01-15 15:13   ` [gentoo-dev] " Christian Faulhammer

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=20081220135444.03efc830@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --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