On Fri, 12 Aug 2005, Junio C Hamano wrote:
>
> I have never liked the original -script name convention. It
> only meant that they are implemented as scripts (as opposed to
> those on the $(PROG) Makefile variable), but the end users who
> end up typing their names from the command line, and to a lesser
> degree the people who use them in their scripts, should not care
> how they are implemented to begin with.
Well, end users _don't_ care, since they are supposed to use just a simple
"git xxx".
The advantage with "git-xxx-script" is for git developers: at least yours
truly does "grep xyz *.c" all the time, and the "grep abc *-script" is
entirely analogous to that. That's where the "-script" ending comes from:
it really helps pick out the stuff you can grep from (as opposed to the
stuff that got compiled and isn't greppable).
Sure, I could have called it ".sh" instead to make it look even more like
a shell script thing, but I actually think "-script" describes any
scripting language - shell, perl, you name it..
Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
