Git development
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: git@vger.kernel.org
Subject: Re: git-svn: multiple branches directories
Date: Sun, 8 Jun 2008 20:51:40 +0200	[thread overview]
Message-ID: <20080608185140.GA31698@atjola.homenet> (raw)
In-Reply-To: <20080608183742.GF23243@xorcom.com>

On 2008.06.08 21:37:42 +0300, Tzafrir Cohen wrote:
> On Sun, Jun 08, 2008 at 12:00:58PM -0400, Steven Walter wrote:
> > On Sat, Jun 7, 2008 at 8:23 PM, Tzafrir Cohen <tzafrir.cohen@xorcom.com> wrote:
> > > Hi
> > >
> > > Does git-svn support a repository layout where branches may reside under
> > > more than one root?
> > >
> > > /trunk
> > > /branches
> > >  branch1
> > >  branch2
> > >  branch3
> > > /somedir
> > >  branch4
> > >  branch5
> > >  branch6
> > > /tags
> > >  ...
> > 
> > git-svn does support it.  The way that I interact with repositories
> > like this is to have the main git-svn remote track only the trunk
> > (fetch = /trunk:...), and then to add addititonal remotes for each
> > branch that I want to track.  There may be a nicer way to do it, but
> > git-svn certainly supports the method just described.
> 
> Thanks for your answer,
> 
> I'm afraid I don't follow you. Where do I have to write that and where?

You can just add more svn-remote to a single git repo with "git svn
init". So you could do:

git svn clone -s svn://host/some/repo
cd repo
git svn init --branches somedir svn://host/some/repo/ svn2
git svn fetch svn2

To fetch all new stuff at once, you would then later use "git svn fetch
--all".

Björn

      reply	other threads:[~2008-06-08 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08  0:23 git-svn: multiple branches directories Tzafrir Cohen
2008-06-08 16:00 ` Steven Walter
2008-06-08 18:37   ` Tzafrir Cohen
2008-06-08 18:51     ` Björn Steinbrink [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=20080608185140.GA31698@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --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