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

Re: git-svn of both trunk and tags while having no access to the 'parent' of those

From
EWEric Wong <normalperson@yhbt.net>
Date
Nov 20, 2009, 20:47 UTC
Message-ID
<20091120204723.GB30423@dcvr.yhbt.net>
In-Reply-To
<20091119095307.GA30423@dcvr.yhbt.net>
Eric Wong <normalperson@yhbt.net> wrote:
Show 9 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> wrote:
> > I tried also with two svn sections to circumvent this:
> > 
> > [svn-remote "svn"]
> >         url = http://domain.com:/project/trunk
> >         fetch = :refs/remotes/trunk
> > [svn-remote "svnr"]
> >         url = http://domain.com:/project/releases
> >         tags = /*:refs/remotes/tags/*
Hi Yaroslav,

Weird, I'm a bit confused by this myself but I'm out of time at the moment, but swapping '[svn-remote "svn"]' and "[svn-remote "svnr"]" seems to work, so there's apparently a bug in our handling of svn-remote != "svn" somewhere...

So the following config should work:
[svn-remote "svnt"]
        url = http://domain.com:/project/trunk
        fetch = :refs/remotes/trunk
[svn-remote "svn"]
        url = http://domain.com:/project/releases
        tags = /*:refs/remotes/tags/*

You should probably run "git svn fetch -R svnt" before running "git svn fetch" to pick up the tagged releases.

-- 
Eric Wong
Previous: Eric WongNext: Eric Wong
Message 8 of 9 in “git-svn of both trunk and tags while having no access to the 'parent' of those”
  1. Yaroslav HalchenkoNov 17, 2009
  2. Michael J GruberNov 18, 2009
  3. Yaroslav HalchenkoNov 18, 2009
  4. Michael J GruberNov 18, 2009
  5. Yaroslav HalchenkoNov 18, 2009
  6. Michael J GruberNov 18, 2009
  7. Eric WongNov 19, 2009
  8. Eric WongNov 20, 2009
  9. git svn: always reuse existing remotes on fetchEric Wong, Nov 22, 2009

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.