git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-svn: mangle refnames forbidden in git

From
EWEric Wong <normalperson@yhbt.net>
Date
Jul 8, 2010, 08:58 UTC
Message-ID
<20100708085814.GC10779@dcvr.yhbt.net>
In-Reply-To
<20100708084356.GA29856@burratino>
Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 15 quoted lines
> 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.
<snip>
Show 6 quoted lines
>  $ svn --version
>  svn, version 1.6.12 (r955767)
>     compiled Jun 21 2010, 20:24:54
>  [...]
> 
> Ideas?

I can't reproduce it with 1.5.1 here, does URI-escaping the "@{0}" to "%40%7B0%7D" work?

-- 
Eric Wong
Previous: Jonathan NiederNext: Jonathan Nieder
Message 4 of 9 in “git-svn: mangle refnames forbidden in git”
  1. git-svn: mangle refnames forbidden in gitTorsten Schmutzler, May 6, 2010
  2. Eric WongMay 9, 2010
  3. Jonathan NiederJul 8, 2010
  4. Eric WongJul 8, 2010
  5. Jonathan NiederJul 8, 2010
  6. Michael J GruberJul 8, 2010
  7. t9118: avoid PEG revision identifier in testsMichael J Gruber, Jul 8, 2010
  8. A Large Angry SCMJul 8, 2010
  9. Eric WongJul 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.