From: Marcel Holtmann <marcel@holtmann.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: Latest cogito broken with bash-3.1
Date: Sun, 11 Dec 2005 09:31:07 +0100 [thread overview]
Message-ID: <1134289867.9541.9.camel@blade> (raw)
In-Reply-To: <20051211001106.GV22159@pasky.or.cz>
Hi Petr,
> > The cogito is the latest from kernel.org and when calling cg-commit it
> > fails with this message:
> >
> > cg-commit: line 200: syntax error near unexpected token `('
> > cg-commit: line 200: ` eval commitfiles=($(cat $filter | path_xargs git-diff-index -r -m HEAD -- | \'
> >
> > I played a little bit with it and it seems all the eval statements are
> > broken with this bash version. I have no clue how to fix this, but maybe
> > you do.
>
> it seems like the newer bash is stricter than the older versions in
> some obscure regards. Quoting the eval arguments (which is the proper
> thing to do anyway) fixed that particular problem; I've hit another
> problem during a test commit wrt. whitespace separators - I've fixed
> that too, and pushed out.
it's now working again. Thanks. What do you think about another release?
I haven't checked the other distributions yet, but I just saw that
Debian unstable also moved to version 3.1 of bash.
There exists also another problem with the new bash. It is the broken
pipe error from cg-log.
cg-log: line 141: echo: write error: Broken pipe
The line number varies depending how much you scrolled and when you
scrolled to the end no broken pipe error comes up. Do you have any idea
on how to deal with this. I saw your comment about that bash is broken
and the extra trap command, but it doesn't help. I never saw that
problem with older versions of bash.
Regards
Marcel
next prev parent reply other threads:[~2005-12-11 8:31 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 [this message]
2005-12-12 0:26 ` Petr Baudis
2005-12-12 0:58 ` Martin Langhoff
2005-12-12 0:59 ` Petr Baudis
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=1134289867.9541.9.camel@blade \
--to=marcel@holtmann.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).