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

Re: git-svn problems with branches containing spaces

From
JHJan Hudec <bulb@ucw.cz>
Date
Jul 10, 2007, 18:33 UTC
Message-ID
<20070710183328.GB4808@efreet.light.src>
In-Reply-To
<20070710134236.2870.qmail@986bac8bfff25d.315fe32.mid.smarden.org>
On Tue, Jul 10, 2007 at 13:42:35 +0000, Gerrit Pape wrote:
Show 18 quoted lines
> On Wed, Jun 27, 2007 at 08:53:06AM +0200, Ewald, Robert wrote:
> > As I have reported yesterday on IRC, git-svn has problems with branches
> > containing spaces.
> > I get the following message, when I want to clone from the repository
> > containing a branch with a space.
> > Cloning until the revision the branch is created everything works fine.
> > 
> > fatal: refs/remotes/Modbus Error Limit Fix: cannot lock the ref
> > update-ref -m r1897 refs/remotes/Modbus Error Limit Fix
> > ff0819c8e9c97c24e9865bc868c503fd9b64f980: command returned error: 128
> > 
> > Thanks for your help.
> 
> Hi, the same problem has been reported some time ago through
>  http://bugs.debian.org/430518
> 
> There's a patch attached to the report, but from a first glance, I don't
> think it's the solution.

It depends on whether it's OK for git to have refs with funny characters in them. If it is, than the patch would be a fix. If not, than the escaping the patch removes needs to be added to all other places that have any business with refs.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Gerrit PapeNext: Eric Wong
Message 3 of 4 in “git-svn problems with branches containing spaces”
  1. Ewald, RobertJun 27, 2007
  2. Gerrit PapeJul 10, 2007
  3. Jan HudecJul 10, 2007
  4. Eric WongJul 11, 2007

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.