From: "brian m. carlson" <sandals@crustytoothpaste.ath.cx>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Reorder msgfmt command-line arguments.
Date: Mon, 3 Dec 2007 17:04:02 +0000 [thread overview]
Message-ID: <20071203170402.GA13712@crustytoothpaste.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.64.0712031034200.27959@racer.site>
On Mon, Dec 03, 2007 at 10:35:33AM +0000, Johannes Schindelin wrote:
>On Mon, 3 Dec 2007, brian m. carlson wrote:
>
>> Any program using getopt or getopt_long will stop processing options
>> once a non-option argument has been encountered, if POSIXLY_CORRECT is
>> set.
>
>So have you tested that msgfmt indeed does not work with the present
>command line?
Yes. I run with POSIXLY_CORRECT set to 1, and it does indeed break. I
wouldn't have fixed it if it had worked.
There are parts of the git testsuite that hang in this case, too, but I
have yet to examine them. Rest assured that there are indeed patches
coming, assuming the problems are fixable.
>Besides, you probably want to send this as a git-gui patch: based on
>git-gui.git, not git.git, and Cc'ed to Shawn Pearce.
Thanks. Will do.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
next prev parent reply other threads:[~2007-12-03 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 1:26 [PATCH] Reorder msgfmt command-line arguments brian m. carlson
2007-12-03 10:35 ` Johannes Schindelin
2007-12-03 17:04 ` brian m. carlson [this message]
2007-12-03 18:05 ` Johannes Schindelin
2007-12-04 2:07 ` Shawn O. Pearce
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=20071203170402.GA13712@crustytoothpaste.ath.cx \
--to=sandals@crustytoothpaste.ath.cx \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).