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

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

From
AKAlbert Krawczyk <pro-logic@optusnet.com.au>
Date
Dec 13, 2010, 00:55 UTC
Message-ID
<000401cb9a60$71bcd610$55368230$@optusnet.com.au>
In-Reply-To
<m2fwu2ecy8.fsf@igel.home>
Andreas Schwab [mailto:schwab@linux-m68k.org]
> If they are multiple projects then you'll probably be better off 
> importing each project into its own git repository.
> 
> Andreas.

Yes, this is probably the 'better' way of dealing with it, and it works fine. I was however wondering if there was a way to track the root of the SVN directory with the structure I supplied earlier while maintaining a 'nice' structure in Git without having /trunk/, /branch/, /tag/ subdirectories appearing directly in the repository as standard folders. My (extremely limited) understanding is that I would need to edit the config file, specifically the fetch, branches and tags section of svn-remote. But I am unsure of how this modified section would look like. 

Albert
Previous: Andreas SchwabNext: Stephen Bash
Message 3 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.