git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dherring@ll.mit.edu
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-svn: how to connect SVN branches?
Date: Fri, 18 Jan 2008 09:43:44 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.0.999999.0801180932310.3479@mojave> (raw)
In-Reply-To: <478FD0E5.2080006@vilain.net>

Sam, Gregory, thanks for solving my problem.

On Thu, 17 Jan 2008, Sam Vilain wrote:
> dherring@ll.mit.edu wrote:
>> `git-svn fetch` pulled the new branch.  However, it created a whole new
>> history for this branch (new git commits from the beginning of the SVN
>> repo).
>>
>> Is there some way to tell git/git-svn to connect these two histories?
>
> git-svn doesn't yet support arbitrary mapping of paths like that.  You
> need to add a separate git-svn remote, and you might have to graft to
> get it started - see below.
>
>> Pictorially, I have
>>
>> SVN1@a---SVN2@a---SVN3@b---SVN4@b---SVNtrunk
>> SVN1@b---SVN2@b---SVN3@b---SVN4@b---SVNbranch
>
> That's unfortunate.  There are many things that git-svn does to try to
> avoid this happening.  You can fix it using the .git/info/grafts
> facility - check the Documentation/ for information on that.  Once
> you've got it looking right, git filter-branch can be used to make it
> permanent, though you should certainly delete the git-svn metadata after
> using that.

Documentation/repository-layout.txt had the best info on grafts.  A few 
graft lines and my git repo looks just right.  For now, I'm scared of 
breaking git-svn again; filter-branch can wait for later.

Thanks again,
Daniel

  reply	other threads:[~2008-01-18 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 20:17 git-svn: how to connect SVN branches? dherring
2008-01-17 22:04 ` Sam Vilain
2008-01-18 14:43   ` dherring [this message]
2008-01-17 23:42 ` Gregory Jefferis

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=alpine.LNX.0.999999.0801180932310.3479@mojave \
    --to=dherring@ll.mit.edu \
    --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).