From: Jonathan Nieder <jrnieder@gmail.com>
To: Torsten Schmutzler <git-ts@theblacksun.eu>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH] git-svn: mangle refnames forbidden in git
Date: Thu, 8 Jul 2010 03:43:57 -0500 [thread overview]
Message-ID: <20100708084356.GA29856@burratino> (raw)
In-Reply-To: <4BE3249B.7050100@theblacksun.eu>
t9118-git-svn-funky-branch-names.sh fails for me:
[...]
3402a8497588142722deb77f6e4f42b6caaabc85
refs/remotes/not-a%40{0}reflog
fatal: ambiguous argument 'refs/remotes/not-a%40{0}reflog': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
not ok - 2 test clone with funky branch names
More precisely, the failure occurs in the
svn_cmd cp -m "reflog" "$svnrepo/pr ject/trunk" \
"$svnrepo/pr ject/branches/not-a@{0}reflog" &&
line in that test: I think svn is handling the @ itself here.
$ svnadmin create /tmp/foo
$ svn checkout file:///tmp/foo wc
Checked out revision 0.
$ echo hello >wc/source
$ (cd wc && svn add source)
A source
$ (cd wc && svn commit -m one)
Adding source
Transmitting file data .
Committed revision 1.
$ svn cp -m reflog file:///tmp/foo/source 'file:///tmp/foo/not-a@{0}reflog'
Committed revision 2.
$ (cd wc && svn update)
A not-a
Updated to revision 2.
$ svn --version
svn, version 1.6.12 (r955767)
compiled Jun 21 2010, 20:24:54
[...]
Ideas?
next prev parent reply other threads:[~2010-07-08 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 20:20 [PATCH] git-svn: mangle refnames forbidden in git Torsten Schmutzler
2010-05-09 8:35 ` Eric Wong
2010-07-08 8:43 ` Jonathan Nieder [this message]
2010-07-08 8:58 ` Eric Wong
2010-07-08 13:03 ` Jonathan Nieder
2010-07-08 18:53 ` Michael J Gruber
2010-07-08 19:16 ` [PATCH] t9118: avoid PEG revision identifier in tests Michael J Gruber
2010-07-08 19:33 ` A Large Angry SCM
2010-07-08 20:38 ` Eric Wong
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=20100708084356.GA29856@burratino \
--to=jrnieder@gmail.com \
--cc=git-ts@theblacksun.eu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
/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).