From: Petr Baudis <pasky@suse.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: git@vger.kernel.org
Subject: Re: Latest cogito broken with bash-3.1
Date: Sun, 11 Dec 2005 01:11:06 +0100 [thread overview]
Message-ID: <20051211001106.GV22159@pasky.or.cz> (raw)
In-Reply-To: <1134220724.15125.4.camel@blade>
Hello,
Dear diary, on Sat, Dec 10, 2005 at 02:18:44PM CET, I got a letter
where Marcel Holtmann <marcel@holtmann.org> said that...
> 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.
Thanks,
--
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-11 0:11 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 [this message]
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
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=20051211001106.GV22159@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).