From: Petr Baudis <pasky@suse.cz>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, git@vger.kernel.org
Subject: Re: Latest cogito broken with bash-3.1
Date: Mon, 12 Dec 2005 01:59:44 +0100 [thread overview]
Message-ID: <20051212005944.GX22159@pasky.or.cz> (raw)
In-Reply-To: <46a038f90512111658x5fe3198ey38515fc2745dd42b@mail.gmail.com>
Dear diary, on Mon, Dec 12, 2005 at 01:58:00AM CET, I got a letter
where Martin Langhoff <martin.langhoff@gmail.com> said that...
> On 12/12/05, Petr Baudis <pasky@suse.cz> wrote:
> > Then that's quite funny, one-line broken pipe message has been always
> > there (in the past it looked much worse, we thankfully managed to bring
> > it down to this at least).
>
> I assume there's no reasonable workaround to that then?
The trapping is apparently the best we can do - at least I know of
nothing better.
> What would take to get rid of that (say, if I had a boring weekend ;)?
Fixing bash, IIRC - and more importantly, convincing its maintainers to
take the patch. ;-) Sometime in the spring someone even posted the exact
location in bash where this is broken.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-12-12 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 13:18 Latest cogito broken with bash-3.1 Marcel Holtmann
2005-12-11 0:11 ` Petr Baudis
2005-12-11 8:31 ` Marcel Holtmann
2005-12-12 0:26 ` Petr Baudis
2005-12-12 0:58 ` Martin Langhoff
2005-12-12 0:59 ` Petr Baudis [this message]
2005-12-12 9:30 ` Marcel Holtmann
2005-12-12 10:40 ` Petr Baudis
2005-12-12 11:02 ` Marcel Holtmann
2005-12-12 15:32 ` Linus Torvalds
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=20051212005944.GX22159@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=martin.langhoff@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).