Re: How to clone git repository with git-svn meta-data included?

From: Sam Vilain <sam@vilain.net>
Date: Dec 9, 2008, 09:08 UTC
Message-ID: <1228813734.28186.77.camel@maia.lan>
In-Reply-To: <493D6AE9.6020504@tuffmail.com>

On Mon, 2008-12-08 at 19:43 +0100, Grzegorz Kossakowski wrote:

Show 11 quoted lines

> > Yes. The rfoo = sha1hash part is git-svn rebuilding its index.
> > "Current branch master is up to date" is git-svn calling "git rebase
> > <svn-branch>", and git saying that there is nothing to do, since there
> > have been no svn commits to that branch since the last time you ran
> > git svn rebase (or since you cloned the git mirror, or since the last
> > time the git mirror pulled from svn).
> 
> Thanks for confirmation and explanation.
> 
> The remaining question is who should address this issue with non-existing trunk ref? Should I ask
> Jukka, who maintains svn mirrors, to put instruction into his scripts that will add trunk reference?

It's up to the git-svn user to make sure that they prepare the refs to be what git-svn expects. This is something probably requiring more documentation and/or git-svn features to be easier.

> Would it be the best practice?

Well, obscure stuff should never really be best practice. The best practice is to have a single git repository that is where the svn -> git migration happens. And git-svn could perhaps auto-init based on information in the commit log or something. Best practice is to enhance the tool to work the way it Should(tm) :)

Sam