Re: [PATCH 2/2] bundle: rewrite builtin to use parse-options

Hi,

Jonathan Nieder wrote:

Ramkumar Ramachandra wrote:

quoted

Sure, you can't create a
bundle named "verify", but that's the compromise you'll have to make
if you don't want to type out "--" with each option, no?

Having to type "--" or prefix with "./" to escape ordinary filenames
that do not start with "-" would be completely weird.

Hm, do you have any suggestions to work around this?  Can we use
something like a parse-stopper after the the first subcommand is
encountered, and treat the next argument as a non-subcommand (filename
or whatever else)?

-- Ram