> But if the GIT back end is resurrected, it might still be useful to
> bootstrap the GIT side (provided that it is adapted to use the same
> algorithm).
Bootstrapping is no problem with the Git backend -- Darcs push can do it.
> Is the approach it uses documented somewhere? Does it rebase on the
> GIT side to reflect the darcs patch ordering?
No, it doesn't. The Git ordering should be taken up to commutation.
> I had no luck at all with the GIT backend, and its remnants prevent
> people from using tailor and its combined darcs/GIT repositories.
> At least that should be addressed.
Yes.
>> May I encourage you to consider working on the Git backend instead,
>> which does (or, more precisely, did) have these features?
> I believe a reasonable precondition for a GIT backend would be the
> conclusion of the GIT libification project, right?
I believe it's been done. At least, libgit is sufficiently complete
for darcs-git.
Juliusz
_______________________________________________
darcs-devel mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-devel
