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: "'Stephen Bash'" <bash@genarts.com>
Cc: <git@vger.kernel.org>
Subject: RE: Git SVN non-standard branch/tag/trunk layout
Date: Tue, 14 Dec 2010 08:08:28 +1100	[thread overview]
Message-ID: <002301cb9b09$e4eb2de0$aec189a0$@optusnet.com.au> (raw)
In-Reply-To: <13731475.185564.1292250200171.JavaMail.root@mail.hq.genarts.com>

>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.
>
>HTH,
>Stephen

Hi Stephen,

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. 

Thanks again for clarifying that,
Albert 

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 21:35 Git SVN non-standard branch/tag/trunk layout Albert Krawczyk
2010-12-13  0:25 ` Andreas Schwab
2010-12-13  0:55   ` Albert Krawczyk
2010-12-13 14:23 ` Stephen Bash
2010-12-13 21:08   ` Albert Krawczyk [this message]
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='002301cb9b09$e4eb2de0$aec189a0$@optusnet.com.au' \
    --to=pro-logic@optusnet.com.au \
    --cc=bash@genarts.com \
    --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).