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

Re: git-svn: multiple branches directories

From
Steven Walter <stevenrwalter@gmail.com>
Date
Jun 8, 2008, 16:00 UTC
Message-ID
<e06498070806080900x4ecd730byefedf88aa4feee5e@mail.gmail.com>
In-Reply-To
<20080608002349.GB23243@xorcom.com>
On Sat, Jun 7, 2008 at 8:23 PM, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote:
Show 16 quoted lines
> Hi
>
> Does git-svn support a repository layout where branches may reside under
> more than one root?
>
> /trunk
> /branches
>  branch1
>  branch2
>  branch3
> /somedir
>  branch4
>  branch5
>  branch6
> /tags
>  ...

git-svn does support it. The way that I interact with repositories like this is to have the main git-svn remote track only the trunk (fetch = /trunk:...), and then to add addititonal remotes for each branch that I want to track. There may be a nicer way to do it, but git-svn certainly supports the method just described.

-- 
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
 -Robert Heinlein
Previous: Tzafrir CohenNext: Tzafrir Cohen
Message 2 of 4 in “git-svn: multiple branches directories”
  1. Tzafrir CohenJun 8, 2008
  2. Steven WalterJun 8, 2008
  3. Tzafrir CohenJun 8, 2008
  4. Björn SteinbrinkJun 8, 2008

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.