Hi All,

I have posted on this mailing list before (and reported bugs) about
various Darcs performance issues.
Ultimately it means I can no longer use Darcs on my old large repo.  I
have since moved to another DVCS
and took a snapshot of the tree of the old repo and used that as a
starting point for the new history.

I have tried many different conversion tools (tailor, darcs-2-git etc)
but they all invoke Darcs under the hood
and on my large repo Darcs hits the exponential time/space issue (yes,
even Darcs 2).

So I took it upon myself to reverse engineer the Darcs patch format
and see if I could create a tool that
could recreate the tree patch by patch and commit to another DVCS as
it went along.

I have had some degree of success, but have hit a few roadblocks and
am beginning to question my understanding
of the inventory and patch format, and how to apply it.

Essentially, I can export a > 2000 patch repo in 30 minutes-ish to
Git.  Unfortunately the resulting tree is
not identical to the original tree in the Darcs repo - lines are not
in the correct place in a significant number of files,
some .gz files seem to contain identical hunks and get applied twice etc.

I realise it's a big ask - but if *anybody* could take a look at my
GitHub repo, starting off with the README file
where I have documented my understanding of the inventory and patches
I would be *incredibly* grateful.

I am getting more than a little desperate.  As it stands, my old
history is lost forever and this tool is my last chance
to get it back.

The GitHub URL for my converter:
http://github.com/freshtonic/darcs-fast-export/tree/master

The clone URL:
git://github.com/freshtonic/darcs-fast-export.git

Thanks in advance for any advice/code/time.

James.

-- 
Walt Disney  - "I love Mickey Mouse more than any woman I have ever known."
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to