Problem exporting to git

[Chris Hecker]

This probably doesn't help you, but when I switched from svn to bzr, I 
had to write a bunch of filters and hack existing scripts and whatnot to 
get everything to import, and my repo was relatively simple.  I think 
there's no robust tool for this because nobody does it often, you just 
hack it until you get yours imported to wherever you're going and then 
try to never think about it again.

Chris




On 2014-03-04 12:05, Frits Jalvingh wrote:
>  > Indeed, there aren't any current tools that do such things,
>> unfortunately.
>
> At the risk of sounding cynical, so far no tool even succeeds at
> exporting anything /at all/ from my repository, a 100% failure rate -
> which is scary. That's worse than "losing" information that the target
> system cannot hold anyway: it is losing all history. I think retaining
> things like renames etc. in commits might be useful for roundtripping
> tasks, but for one-shot migration they are not useful - considering that
> after the move the "new" vcs does not support the data anyway...
>
>
> On Tue, Mar 4, 2014 at 2:41 PM, Stephen J. Turnbull <stephen at xemacs.org
> <mailto:stephen at xemacs.org>> wrote:
>
>     Jelmer Vernooij writes:
>       > On Mon, Mar 03, 2014 at 09:35:26PM +0100, Frits Jalvingh wrote:
>       > > > You lose that metadata regardless of the method you use to
>     push from bzr
>       > > into git.
>       > >
>       > > When we talk about "metadata" in this respect - is it only
>     renames? Because
>       > > that should not be a problem - considering that git does not
>     track renames
>       > > at all?
>       > The main ones are renames, empty directories, revision
>     properties (bug fix
>       > information, authors beyond the first author).
>       >
>       > > Considering that the goal is to switch completely from bzr to
>     git, I assume
>       > > losing that data is meaningless?
>
>     It can't be represented in the same way, but it can be represented,
>     for example by some convention in the log message or a git note for
>     additional authors and bug fixes, empty directories can use the
>     historic ".precious" file hack, and by confirming and resigning the
>     signature for signatures (since Ben mentions them).  Renames you hope
>     that git's automatic detection (which is pretty reliable in most
>     projects) is good enough.  So the loss of information is not
>     "meaningless" in the sense that you couldn't somehow transfer it to
>     git.
>
>     However:
>
>       > Yes, if you're migrating then that data is going to be lost
>       > regardless of the migration tool you use.
>
>     Indeed, there aren't any current tools that do such things,
>     unfortunately.
>
>