git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: David Brown <git@davidb.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn and hierarchal branches.
Date: Tue, 02 Oct 2007 00:45:37 +1300	[thread overview]
Message-ID: <4700DDE1.2000906@vilain.net> (raw)
In-Reply-To: <20070930070754.GA10264@old.davidb.org>

David Brown wrote:
> I'm trying to use git-svn to track the 'Tango' SVN repository
> <http://www.dsource.org/projects/tango/wiki/Download>
>
> Their layout is mostly standard, except that they have an extra hierarchy
> in the branch directory (branch/user1, branch/user2, branch/D1_0 for a
> release).
>
> Is this something I can easily track with git-svn, or am I best trying to
> do it manually?

Track each branch with a separate git-svn remote.

Sam.

      reply	other threads:[~2007-10-01 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30  7:07 git-svn and hierarchal branches David Brown
2007-10-01 11:45 ` Sam Vilain [this message]

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

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

  git send-email \
    --in-reply-to=4700DDE1.2000906@vilain.net \
    --to=sam@vilain.net \
    --cc=git@davidb.org \
    --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.
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 NNTP newsgroup(s).