[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [BUG?] Re: fail to svn clone debian's kernel repository
From:       Sebastian Pipping <webmaster () hartwork ! org>
Date:       2010-03-04 2:03:19
Message-ID: 4B8F14E7.5050000 () hartwork ! org
[Download RAW message or body]

On 03/03/10 15:33, Thomas Rast wrote:
> Combining this fix with the above config results in correct
> "continuous" history of trunk, whereas merely using the config above
> results in a disconnect at the move.

Thanks for your time to look into that!

After applying your ideas (which seem to work well) I end up with:
==================================================================
git svn init file://"${ABS_SVN_SOURCE}"
git config svn-remote.svn.fetch 'trunk:refs/remotes/trunk@1889'
git svn fetch -r1:1889
git svn init file://"${ABS_SVN_SOURCE}" \
  --trunk=main/trunk
git config svn-remote.svn.tags 'main/tags/*:refs/tags/*'
git config svn-remote.svn.branches 'main/branches/*:refs/heads/*'
git svn fetch -r1890:HEAD
==================================================================

.git/config holds:
==================================================================
[..]
[svn-remote "svn"]
        url = file:///[..]/portage-anon-svn-repo-dump
        fetch = trunk:refs/remotes/trunk@1889
        fetch = main/trunk:refs/remotes/trunk
        tags = main/tags/*:refs/tags/*
        branches = main/branches/*:refs/heads/*
==================================================================

Thought I'd paste that if anybody else is interested.



Sebastian
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]