From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: bash-4.0 regression heads up (escaped semicolons in subshells)
Date: Sun, 22 Feb 2009 13:10:38 +0530 [thread overview]
Message-ID: <8b4c83ad0902212340i2f8ca3bcp2f217ef8f3497e11@mail.gmail.com> (raw)
In-Reply-To: <200902212029.00333.vapier@gentoo.org>
On Sun, Feb 22, 2009 at 6:58 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> i guess i used too many code words like "bash-4.0 is broken" and "workaround".
> i'll address this in the future by just mailing base-system@gentoo.org as they
> should be familiar with these insider terms.
Cool it with the war of words folks :)
Mike, thanks for the heads-up regarding bash-4.0, it's really helpful
to have exchange of information to prevent a communication gap (which
only results in conflict).
Mart, if something is unclear, explicitly asking it would be better
than replying with (possibly false) assumptions. Although I agree that
context *is* important for us mere mortals (mike, *hint hint* ;)
This was your daily dose of chuckles, huggles, and fun,
Cheers,
~Nirbheek Chauhan
next prev parent reply other threads:[~2009-02-22 7:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 23:27 [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) Mike Frysinger
2009-02-21 23:38 ` [gentoo-dev] " Ryan Hill
2009-02-21 23:55 ` Mike Frysinger
2009-02-22 0:00 ` Mart Raudsepp
2009-02-22 0:29 ` Mike Frysinger
2009-02-22 0:38 ` Mart Raudsepp
2009-02-22 0:44 ` Mike Frysinger
2009-02-22 0:54 ` Mart Raudsepp
2009-02-22 1:28 ` Mike Frysinger
2009-02-22 7:40 ` Nirbheek Chauhan [this message]
2009-02-24 15:52 ` Daniel Gryniewicz
2009-02-24 15:56 ` Mike Frysinger
2009-02-22 1:02 ` Ryan Hill
2009-02-22 22:30 ` [gentoo-dev] " Dawid Węgliński
2009-02-22 22:39 ` Mike Frysinger
2009-02-22 23:03 ` Dawid Węgliński
2009-02-23 0:00 ` Mike Frysinger
2009-02-24 4:16 ` 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=8b4c83ad0902212340i2f8ca3bcp2f217ef8f3497e11@mail.gmail.com \
--to=nirbheek@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