On Tue, 2007-11-06 at 10:12 +0100, Pierre Habouzit wrote:
> On Mon, Nov 05, 2007 at 11:18:36PM +0000, Johannes Schindelin wrote:
> > Hi,
> >
> > On Mon, 5 Nov 2007, Bj?rn Steinbrink wrote:
> >
> > > On 2007.11.05 13:57:53 -0500, Kristian H?gsberg wrote:
> > >
> > > > The shell script just has
> > > >
> > > > case "$all,$interactive,$also,$#" in
> > > > *t,*t,*)
> > > > die "Cannot use -a, --interactive or -i at the same time." ;;
> > > >
> > > > which doesn't seem to care about the value of $also. As far as I
> > > > understand git commit, it doesn't make sense to pass any of -a, -i, -o
> > > > or --interactive at the same time so I guess I could join the checks
> > >
> > > Note that there are only two commas. The asterisks catch everything and
> > > $# won't be "t", so that catches anything with at least two t's.
> >
> > So shouldn't it be
> >
> > if (!!all + !!interactive + !!also > 1)
>
> Btw, I'm starting to work slowly on the diff_opt_parse conversion to the
> macro we discussed, and the need for new option parsing callbacks
> arised, and I've created a:
>
> parse_opt_mask_{or,and,xor} commands that you declare this way:
>
> OPT_MASK_OR('a', "all", &mode, "...", MASK_ALL),
> OPT_MASK_OR('i', "interactive", &mode, "...", MASK_INTERACTIVE),
> ...
That's useful here, and it should be useful in a lot of other places
using parse_options() where we end up or'ing flags into a mask based on
boolean options.
cheers,
Kristian
-
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
