From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: git <git@vger.kernel.org>
Subject: cvsimport and branches with "(" in the name
Date: Tue, 29 Apr 2008 08:22:02 +0100 [thread overview]
Message-ID: <320075ff0804290022r56c9f4efx74a13d3502be212@mail.gmail.com> (raw)
git 1.5.4.4 on ubuntu, I cvsimport a repository that has an oddly
named branch - I get
sh: Syntax error: "(" unexpected
Cannot write branch ChapelHill_3_0(iteration2)_esap_demo for update:
Bad file descriptor
though the end of my -v log shows
Tree ID 46f13621661205b02a80d7d431a2c59be500ae45
Parent ID d635ccf06e1cac3afacc4fba6e70bba7f771ead2
Committed patch 1956 (ChapelHill_3_0(iteration2)_esap_demo +0000
2006-12-04 10:28:31)
Commit ID 76c991af0c690d9ae5471c0b661dfba3b3df18c6
and refs/heads has a correctly named file
My guess is something in the guts isn't liking the ( character, when
committing the next patch.
Any ideas on how to diagnose / fix it further ?
next reply other threads:[~2008-04-29 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 7:22 Nigel Magnay [this message]
2008-04-29 15:52 ` cvsimport and branches with "(" in the name Jeff King
2008-04-30 0:45 ` Morten Welinder
2008-04-30 3:31 ` Jeff King
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=320075ff0804290022r56c9f4efx74a13d3502be212@mail.gmail.com \
--to=nigel.magnay@gmail.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).