Re: git fast-export | git fast-import doesn't work
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Nov 26, 2008, 10:18 UTC
- Message-ID
- <492D227C.8020805@drmicha.warpmail.net>
- In-Reply-To
- <alpine.DEB.1.00.0811260113140.30769@pacific.mpi-cbg.de>
Johannes Schindelin venit, vidit, dixit 26.11.2008 01:14:
Show 15 quoted lines
> Hi, > > On Tue, 25 Nov 2008, Ondrej Certik wrote: > >> I would like to export our whole git repository to patches, and then >> reconstruct it again from scratch. Following the man page of "git >> fast-export": >> >> [...] >> >> However, the repository is very different to the original one. It >> contains only 191 patches: > > Can you try again with a Git version that contains the commit > 2075ffb5(fast-export: use an unsorted string list for extra_refs)?
With that commit cherry-picked onto today's master I get the same effect:
A) git fast-import crashes with dump generated by git fast-export -M -C B) git fast-import produces disconnected DAG with dump generated by git fast-export
With git 1.5.4, A) is good but B) is still bad. Bisecting gives me (after remembering to put make in the run script, uhm...)...
...
...tadah:
ae7c5dcef92d46cfc8987fde2c264614fe475bd1 is first bad commit commit ae7c5dcef92d46cfc8987fde2c264614fe475bd1 Author: Alexander Gavrilov <angavrilov@gmail.com> Date: Sun Jul 27 00:52:54 2008 +0400
Support copy and rename detection in fast-export.
Oh well :(
Michael