From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bash-3.1 stable
Date: Tue, 2 Apr 2013 15:34:03 +0200 [thread overview]
Message-ID: <20130402153403.0a85c0a7@portable> (raw)
In-Reply-To: <CAG2jQ8iAtdYRaxjG7s2S5d+od4z7HOZp0p+CvgnryZtFL=2HxQ@mail.gmail.com>
On Tue, 2 Apr 2013 14:07:16 +0100
Markos Chandras <hwoarang@gentoo.org> wrote:
> On 2 April 2013 13:48, Rich Freeman <rich0@gentoo.org> wrote:
> > On Tue, Apr 2, 2013 at 8:37 AM, Alexis Ballier
> > <aballier@gentoo.org> wrote:
> >> but what's the problem with keeping it and not breaking older
> >> upgrade paths?
> >>
> >
> > This whole discussion seems a bit academic. Somebody pointed out
> > that we have a version of bash we might not need any longer. If by
> > some miracle the bash maintainers weren't already aware of it, they
> > are now. If they want to keep it around for some reason, who cares?
> >
> > There is enough bikeshedding when it comes to treecleaning the
> > packages that aren't being maintained. I don't think we need to
> > debate the merits of the packages that are.
> >
> > Rich
> >
>
> I couldn't agree more. It is getting really annoying having to debate
> package removals every other day.
Please take your time to read again. There is no bikeshedding nor
debate in:
- X is not needed anymore because of reasons R
- maybe it's needed for case Y
- case Y is not supported
- it doesn't hurt to support it
I am very well aware that 'case Y' may not even be possible because of
tons of other problems and was only pointing out that 'reasons R' were
incomplete.
It is getting really annoying to have non-technical comments pop in
purely technical discussions ;)
Alexis.
next prev parent reply other threads:[~2013-04-02 13:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 12:25 [gentoo-dev] bash-3.1 stable hasufell
2013-04-02 12:29 ` Alexis Ballier
2013-04-02 12:32 ` hasufell
2013-04-02 12:37 ` Alexis Ballier
2013-04-02 12:48 ` Rich Freeman
2013-04-02 13:07 ` Markos Chandras
2013-04-02 13:34 ` Alexis Ballier [this message]
2013-04-02 14:01 ` Markos Chandras
2013-04-02 14:11 ` Ciaran McCreesh
2013-04-02 14:21 ` Alexis Ballier
2013-04-02 14:26 ` Markos Chandras
2013-04-02 14:35 ` Raymond Jennings
2013-04-02 17:54 ` [gentoo-dev] " Duncan
2013-04-14 21:51 ` [gentoo-dev] OT: was " Gregory M. Turner
2013-04-15 9:49 ` Jeroen Roovers
2013-04-15 16:42 ` Peter Stuge
2013-04-02 14:39 ` [gentoo-dev] " hasufell
2013-04-02 14:43 ` Ben Kohler
2013-04-02 13:28 ` Samuli Suominen
2013-04-02 13:33 ` Peter Stuge
2013-04-02 17:40 ` [gentoo-dev] " Mike Frysinger
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=20130402153403.0a85c0a7@portable \
--to=aballier@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