All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/2] more tests for git rev-parse --parse-opt
Date: Wed, 10 Jun 2009 16:16:14 +0200	[thread overview]
Message-ID: <20090610141614.GA20299@pengutronix.de> (raw)
In-Reply-To: <4A2F8CEC.4080600@viscovery.net>

Hello Johannes,

On Wed, Jun 10, 2009 at 12:37:32PM +0200, Johannes Sixt wrote:
> Uwe Kleine-König schrieb:
> > -test_expect_success 'test --parseopt help output' '
> > -	git rev-parse --parseopt -- -h 2> output.err <<EOF
> > +OPTION_SPEC="\
> >  some-command [options] <args>...
> >  
> >  some-command does foo and bar!
> > @@ -36,8 +35,53 @@ C?        option C with an optional argument
> >  
> >  Extras
> >  extra1    line above used to cause a segfault but no longer does
> > +"
> > +
> > +test_expect_success 'test --parseopt help output' '
> > +	git rev-parse --parseopt -- -h 2> output.err <<EOF
> > +$OPTION_SPEC
> >  EOF
> >  	test_cmp expect.err output.err
> >  '
> 
> You use the same input in this and all new tests; make this:
> 
> cat > optionspec <<EOF
> ...
> EOF
> 
> test_expect_success 'test --parseopt help output' '
> 	git rev-parse --parseopt -- -h 2> output.err < optionspec &&
> 	test_cmp expect.err output.err
> 
> (note the added &&).
OK, this should work.  I will rework it later today.

BTW: I wonder why

	git rev-parse --parseopt -- -h 2> output.err < optionspec

fills output.err, is there some magic that detects that the help should
be printed?  *read some source*  ah, -h is hardcoded to print the help.
This is a bit surprising, still more as -h is a valid option in the
specified optionspec.  Thoughts?

Thanks
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

  reply	other threads:[~2009-06-10 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  8:36 notice: pu broken tonight Junio C Hamano
2009-06-09 17:11 ` René Scharfe
2009-06-10  7:44 ` Uwe Kleine-König
2009-06-10  7:56   ` Junio C Hamano
2009-06-10  9:42     ` [PATCH 1/2] more tests for git rev-parse --parse-opt Uwe Kleine-König
2009-06-10  9:42       ` [PATCH 2/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Uwe Kleine-König
2009-06-10 10:37       ` [PATCH 1/2] more tests for git rev-parse --parse-opt Johannes Sixt
2009-06-10 14:16         ` Uwe Kleine-König [this message]
2009-06-13 23:58           ` Uwe Kleine-König
2009-06-13 23:58             ` [PATCH 2/2] parse-opt: make PARSE_OPT_STOP_AT_NON_OPTION available to git rev-parse Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090610141614.GA20299@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.