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

Git SVN non-standard branch/tag/trunk layout

From
AKAlbert Krawczyk <pro-logic@optusnet.com.au>
Date
Dec 12, 2010, 21:35 UTC
Message-ID
<006c01cb9a44$8407d2f0$8c1778d0$@optusnet.com.au>
Hi all,

One of the SVN repositories that I work with (and have a Git version of) has recently implemented a tag/trunk/branch layout, and I'd like to update my repository to correctly work with this layout.

As far as I understand the standard layout for a SVN repo that supports branching is

SVR Root ----Trunk - folders/files
 \
  --Branch - folders/files
  \
   -Tag - folders/files
With each of those having the project contents

The SVN repo I am now faced with has the trunk/branch/tag folders on selected folders in the tree.

Essentially instead of having one project per repo, there are multiple projects in the repo. So the repo looks like this

---SVN Root --- Folder(Proj1) ---- Files
	\
	 ---- Folder(Proj2) --- Trunk - Files
	|	       \
	|		- Branch - Files
	|		|
	|		- Tag - ...
	|
	|- Proj3 - Files
	|- Proj4 - Trunk
		 |-Branch
		 | - Tag

The question is, is there a way I can get Git SVN to understand and replicate this layout in a git repo? I don't mind if I have to import the entire repo again into git.

Thanks, Albert

Next: Andreas Schwab
Message 1 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.