On Thu, Feb 21, 2008 at 02:46:13PM -0800, Josh Triplett wrote: > 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:
Hi Josh, the difference in your examples is that they all have only options in the sysnopsis. With git-merge-index there're two options that adjust the behavior of git-merge-index (-o, -a) and the other option (-a) adjusts how the <merge-program> will be called. With <merge-program> not being an option but an non-optional argument naming a program, I think the documentation is clear on that the -a option must not be before <merge-program>, just as the <filename>... arguments. Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
