Re: [RFC/PATCH] parse-options: introduce parse_subcommands
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Jun 6, 2012, 14:10 UTC
- Message-ID
- <CALkWK0nuJ2VrAUD5PsfnZzO5yDgB+h4xn8g=CTqmUvJ8DOdPNQ@mail.gmail.com>
- In-Reply-To
- <7vlik3t3j2.fsf@alter.siamese.dyndns.org>
Hi Junio,
Junio C Hamano wrote:
Show 10 quoted lines
> Ramkumar Ramachandra <artagnon@gmail.com> writes: > >> I found this patch in one of my branches from a long time ago. I >> haven't written documentation and tests yet because I'm not fully >> convinced that I like this. >> >> Thoughts? > > It looks like a static version of string_list_lookup() and does not > have much reason to tie it to "subcommand".
How so? I can use a string_list to keep subcommand->name and stuff the callback into util. Where do I put subcommand->help then? I agree that there's no reason to tie it to subcommand though.
Ram