From: John Gateley <gateley@jriver.com>
To: git@vger.kernel.org
Subject: cg-admin-setuprepo
Date: Thu, 5 Apr 2007 11:56:53 -0500 [thread overview]
Message-ID: <20070405115653.b028db2c.gateley@jriver.com> (raw)
Hi,
I'm trying to do a cg-admin-setuprepo directory, and I'm getting
an error:
bash: line 12: syntax error near unexpected token `&&'
bash: line 12: `[[ --ee "/home/gateley/git/firewall.git"" ]] &&&& ddiiee "/home/gateley/git/firewall.gitt aallrreeaaddyy eexxiisstts""'
Looking at the source, the duplicated character problems happen here:
# Careful here, no cg-Xlib functions! Also, mind that the variables
# are substituted _before_ executing the script, not as we go. Which
# is somewhat unfortunate in case the user passed us a path containing
# quotes or backslashes, but only sick people do that and they receive
# what they deserve. ;-)
_git="$uri"
cat <<_SCRIPT_EOF_ | $shell $shellarg
die() { echo "$*" >&2; exit 1; }
The "$*" is where the doubled characters begin.
I'm not enough of a shell programmer to know what's happening.
Any ideas?
Thanks and please cc me on replies - I'm not on the mailing list yet...
j
reply other threads:[~2007-04-05 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070405115653.b028db2c.gateley@jriver.com \
--to=gateley@jriver.com \
--cc=git@vger.kernel.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).