Gerrit Pape wrote: > On Wed, Feb 20, 2008 at 04:20:22PM -0800, Josh Triplett wrote: >> git-merge-index requires that if the -o and -q options appear, they >> must appear first in the argument list, and they must appear in that >> order. For example, "git merge-index -o merge-program -a" works, but >> "git merge-index merge-program -o -a" does not work. git-merge-index >> should allow the -o, -q, and -a options to appear anywhere on the >> command line. > > Hi Josh, AFAICS the behavior matches the documentation > > $ git-merge-index > usage: git-merge-index [-o] [-q] <merge-program> (-a | <filename>*) > $ > > Setting severity wishlist.
The same usage syntax in other programs does not imply an order to the
options. "man gcc" says:
gcc [-c|-S|-E] [-std=standard]
[-g] [-pg] [-Olevel]
[-Wwarn...] [-pedantic]
[-Idir...] [-Ldir...]
[-Dmacro[=defn]...] [-Umacro]
[-foption...] [-mmachine-option...]
[-o outfile] [EMAIL PROTECTED] infile...
Yet gcc accepts options in any order.
"man man" says:
man [-c|-w|-tZ] [-H[browser]] [-T[device]] [-X[dpi]] [-adhu7V] [-i|-I]
[-m system[,...]] [-L locale] [-p string] [-C file] [-M path] [-P
pager] [-r prompt] [-S list] [-e extension] [--warnings [warnings]]
[[section] page ...] ...
Yet man accepts options in any order.
"man make" says:
make [ -f makefile ] [ options ] ... [ targets ] ...
Yet make accepts the -f option anywhere on the command line.
- Josh Triplett
signature.asc
Description: OpenPGP digital signature
