Re: [RFC, PATCH] Usage message clean-up, take #2

Fredrik Kuivinen [off-list ref] writes:

The scripts will also set USAGE and possibly LONG_USAGE before they
source git-sh-setup. If LONG_USAGE isn't set it defaults to USAGE.

Looks like a good start to allow us to mechanically generate
parts of the manpages in the future.

Last time I played around with various bourne derivative shells,
I was annoyed by that scripts sourced with '.'  behaved slightly
differently regarding positional arguments such as "$1", which
may be one thing to watch out for (sorry, I do not remember the
details right now, other than one case: ". ./foobra.sh arg1
arg2", and depending on the shell the value of $# and $1
foobra.sh sees was different.  I do not think this would matter
for our purpose because in our case ". script" form is never
used with extra parameters).