Bertram Felgenhauer wrote: > I'm leaning towards b), mainly because I don't think it would be fair > to put the burden of maintaining the code on the darcs developers,
I lean the other way because - It's only a hundred lines of code, once the darcs and git libraries are factored out. (I do believe libgit should be a dependency, just like libdarcs.) - My main point: I think it's a strategic and essential feature for darcs (easy-as-possible interchange with other rcs's, most especially git.) It should be available out of the box, and the user shouldn't have to get a special tool, possibly out of sync with their darcs. Within darcs it will be kept up to date and it will be one less dependency to manage. > not to mention setting a precedent for adding export-* commands for > all VCSs out there. I think that's a good idea, along with import-*. When git and hg and bzr do this, it's considered a killer feature. Eg the way you can talk to subversion repos out of the box. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
