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

Re: Git SVN non-standard branch/tag/trunk layout

From
SBStephen Bash <bash@genarts.com>
Date
Dec 13, 2010, 21:23 UTC
Message-ID
<19945570.186298.1292275382811.JavaMail.root@mail.hq.genarts.com>
In-Reply-To
<002301cb9b09$e4eb2de0$aec189a0$@optusnet.com.au>
----- Original Message -----
Show 21 quoted lines
> From: "Albert Krawczyk" <pro-logic@optusnet.com.au>
> To: "Stephen Bash" <bash@genarts.com>
> Cc: git@vger.kernel.org
> Sent: Monday, December 13, 2010 4:08:28 PM
> Subject: RE: Git SVN non-standard branch/tag/trunk layout
>
> >Project 2 is an interesting one because it looks like the trunk is at
> >the same level as branches/tags. If that's the case, the 'branches'
> >line above will work (it will treat >the trunk like any other branch
> >-- a very Git-like approach). Also note that those projects that
> >didn't have a 'trunk' directory in SVN I added a 'trunk' on the Git
> >side to keep things consistent -- this is completely optional.
> >
> >Once you get comfortable with the rules governing the config lines,
> >you can pretty much untangle any SVN layout.
> 
> Thanks a lot! I thought this is what I had to do, and had through
> trial and (a lot of) error got to be very close. As far as I can see
> the only 'downside' of this approach is that you can't have the 'root'
> of the SVN repo checked out, you can only have the root of each
> project checked out, as they are all on their own ref.
I hadn't thought about it until now, but you could probably specify fetch=/:refs/remotes/svnroot to have a ref that is the root of the SVN repository...  Might be worth a shot...
Stephen
Previous: Albert Krawczyk
Message 6 of 6 in “Git SVN non-standard branch/tag/trunk layout”
  1. Albert KrawczykDec 12, 2010
  2. Andreas SchwabDec 13, 2010
  3. Albert KrawczykDec 13, 2010
  4. Stephen BashDec 13, 2010
  5. Albert KrawczykDec 13, 2010
  6. Stephen BashDec 13, 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.