Am Montag 27 Oktober 2008 22:07:16 schrieb Miklos Vajna: > You compare Python to C here, but did you realize that in git you can > write your git command in any language you want? Of course it's > recommended to do it in C/shell/perl if you want to get it included in > git.git, but that's just a decision. I was asked explicitely about the difference of writing a Mercurial extension and of writing some addition for git in C, so I answered that. > IIRC the main reason git aliases can't overwrite git commands is because > that would break scripts relying on the output of existing git commands. > Given that I install such an extension, won't my script break? Since that "script" will likely be an extension which will use the core function instead of the UI command, it won't break. Stuff which does command line parsing can naturally break when I change the output. But it can also directly use the advanced features. > From a user's point of view, I think external git commands and such hg > plugins are equal. The user instally the "foo" > extension/command/plugin/whatever and gets the "git/hg foo" command. [snip] > Same for git, as long as it's written in a scripting language; you > should include git-foo in PATH then you can use git foo. Means git can provide additional commands and only has the limitation that I can't overwrite the basic commands, right? But we're slowly moving off topic, aside from "OK, git also has extensions - they are called external commands". Best wishes, Arne -- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :) -- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the history of free software. -- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln. -- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
Attachment:
signature.asc
Description: This is a digitally signed message part.
