All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Korzynski, Aleksander" <aleksander.korzynski@hp.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: underscore in Subversion branch name
Date: Wed, 23 Mar 2011 12:12:55 +0000	[thread overview]
Message-ID: <4D89E3C7.6060302@hp.com> (raw)

Dear Git Support,

I'm cloning a Subversion repository to Git. A bug in Git is triggered by 
an underscore in the name of one of the Subversion branches.

I use the following command (note: some names are changed):

$ git svn clone https://AAA.FFF.com/svnroot/BBB -s

The process dies with the following error (names changed):

> Found possible branch point: https://AAA.FFF.com/svnroot/BBB/trunk/CCC => https://AAA.FFF.com/svnroot/BBB/branches/DD_EEEEEEE, 100
> fatal: Not a valid object name refs/remotes/DD EEEEEEE
> cat-file commit refs/remotes/DD EEEEEEE: command returned error: 128

Note that in the top line, the name of the branch contains an 
underscore: "DD_EEEEEE". However, in the middle line, the branch name 
contains a space: "DD EEEEEE". Apparently, Git at some point translates 
the underscore in the name of the Subversion branch into a space.

I've had a look at the source code and the process dies inside 
resolve_local_globs() in the git-svn script. A command at the beginning 
of that subroutine is:

command(qw#for-each-ref --format=%(refname) refs/#)

When I run the following by hand:

$ git for-each-ref --format='%(refname)' refs

one of the output lines is:

refs/remotes/DD%20EEEEEEE

So it has a sanitised space (%20) at that point already, instead of an 
underscore.

Git version: 1.7.1

Best regards,
Aleksander Korzynski

                 reply	other threads:[~2011-03-23 12:13 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=4D89E3C7.6060302@hp.com \
    --to=aleksander.korzynski@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.