git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Albert Krawczyk" <pro-logic@optusnet.com.au>
To: <git@vger.kernel.org>
Subject: Git SVN non-standard branch/tag/trunk layout
Date: Mon, 13 Dec 2010 08:35:34 +1100	[thread overview]
Message-ID: <006c01cb9a44$8407d2f0$8c1778d0$@optusnet.com.au> (raw)

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

             reply	other threads:[~2010-12-12 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 21:35 Albert Krawczyk [this message]
2010-12-13  0:25 ` Git SVN non-standard branch/tag/trunk layout Andreas Schwab
2010-12-13  0:55   ` Albert Krawczyk
2010-12-13 14:23 ` Stephen Bash
2010-12-13 21:08   ` Albert Krawczyk
2010-12-13 21:23     ` Stephen Bash

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006c01cb9a44$8407d2f0$8c1778d0$@optusnet.com.au' \
    --to=pro-logic@optusnet.com.au \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).