Unification of DVCS Commands

When working on several (open source) projects, several version control systems become problematic. Although they have common operations, I often make the mistake of typing hg add instead of git add.

I remember that some time ago I saw a project that provided access to various version control software tools in the same way, providing basic commit / ci add commands, etc. in the shell. Depending on the repository, it in turn calls hg add or git add, etc.

I saw Amp: http://amp.carboni.ca/ (which seems to be disabled by ATM), any other scenarios like this?

+3
source share
4 answers

I think that combining two (in this case, completely different) version control systems is not a reasonable task. While there are certain commonalities, the differences far outweigh the commonalities. More specifically, while you could map specific commands from one system to a similar command in another system, there would still be strong semantic differences, Mercurial and Git have completely different internal models. Just look at how a branch or Git region is represented.

, "", , , , / ( git -svn).

hg add vs. git add -, , , , .

+10

, . amp ( GitHub ) .
.

, / ( - hg git repo - ) - .

0

I think that was one of the goals of anyvcs , but I donโ€™t know how far I have come.

0
source

There are also Push Me Pull You and Qct , both of which are graphical interfaces with several DVCS.

I did not check their status.

0
source

Source: https://habr.com/ru/post/1763369/


All Articles