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

Ramkumar Ramachandra wrote:

Jonathan Nieder wrote:

quoted

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)?

What's the desired behavior?  Then we can talk about how to implement it.

If the goal is "use parse-options for a command that has subcommands",
see builtin/notes.c.