* Juliusz Chroboczek: > I would like to ask that this should not be included in Darcs.
Sure, no problem, I can keep it on a private branch. 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). > The Git backend works very differently: instead of spawning a Git > command, it directly manipulates Git's data structures. It is > a bidirectional gateway that preserves Git's and Darcs branching > structure. Is the approach it uses documented somewhere? Does it rebase on the GIT side to reflect the darcs patch ordering? 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. > 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? _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
