Hi, On Sun, 4 Nov 2007, Junio C Hamano wrote: > Pierre Habouzit <madcoder@xxxxxxxxxx> writes: > > > Also fix some space versus tabs issues. > > --- > > git-checkout.sh | 99 +++++++++++++++++++++++++++---------------------------- > > 1 files changed, 49 insertions(+), 50 deletions(-) > > > > diff --git a/git-checkout.sh b/git-checkout.sh > > index 8993920..5424745 100755 > > --- a/git-checkout.sh > > +++ b/git-checkout.sh > > @@ -1,6 +1,16 @@ > > #!/bin/sh > > > > -USAGE='[-q] [-f] [-b <new_branch>] [-m] [<branch>] [<paths>...]' > > +PARSEOPT_OPTS=--keep-dashdash > > +OPTIONS_SPEC="\ > > +git-branch [options] [<branch>] [<paths>...] > > +-- > > +b= create a new branch started at <branch> > > +l create the new branchs reflog > > +track tells if the new branch should track the remote branch > > +f proceed even if the index or working tree is not HEAD > > +m performa three-way merge on local modifications if needed > > +q,quiet be quiet > > +" > > Ok, so this is how PARSEOPT_OPTS gets used. I also read in the docs: > It takes on the standard input the specification of the options to parse > and understand, and echoes on the standard ouput a line suitable for > `sh(1)` `eval` to replace the arguments with normalized ones. Why not go the full nine yards and output something which when eval'ed sets the variables correctly (taking the variable names from the option names; long name if available, otherwise short one)? It can also set the command line arguments to what's left after option parsing, with a "set" call. And to prevent funny games with "PARSEOPT_OPTS=blabla git xyz", why not provide a function in git-sh-setup which takes the string as argument, and is called _after_ sourcing git-sh-setup? Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
