Ted Zlatanov <
tzz@...> writes:
Hi Ted,
> ESR> But I think it's worth noting that pretty much all the good
> ESR> things being said about git apply equally to other DVCSes such as
> ESR> Mercurial, bzr, monotone, darcs, and Codeville. All of these
> ESR> have very similar basic models based on commit-before-merge and
> ESR> push/pull operations.
>
> Has there ever been an ELisp-based VCS? Should we at least consider
> it? The advantages are significant for this group of developers, and
> it would certainly benefit other users. The major disadvantage
> (besides having to write the code), I imagine, is incompatibility with
> other VCSs, and that can be addressed by a bridge to CVS/Git/Arch/etc
> as deemed appropriate (similar to the git-svn bridge).
I'd say that this would be a monster-job where we simply don't have the
man-power to do that. And I don't see what those significant advantages
would be. Could you elaborate on that?
IMO an elisp solution would bring at least those drawbacks:
- huge effort to write and maintain it
- since we get it right and reliable it may take very long
- worse performance than a highly optimized C solution
- since emacs is single-threaded any VC operation would block emacs
So my opinion is that we'd be better off to use one of the excellent
existing dVCSs.
Bye,
Tassilo
_______________________________________________
Emacs-devel mailing list
Emacs-devel@...
http://lists.gnu.org/mailman/listinfo/emacs-devel
