Re: [PATCH] commit-tree: utilize parse-options api
- From
Brandon Richardson <brandon1024.br@gmail.com>
- Date
- Feb 26, 2019, 23:42 UTC
- Message-ID
- <CAETBDP7AyYKE2gQY-HbP+LBhYwvf1QXt0-JaEQwnVyr=PjrKMw@mail.gmail.com>
- In-Reply-To
- <33efa988-ea80-d9b4-f4aa-3876331a1dfb@gmail.com>
Hi Andrei,
> > would attempt to translate the option as a tree oid.It was also > > Missing space after period.
Oops, thanks for pointing that out.
Show 6 quoted lines
>
> > + { OPTION_CALLBACK, 'p', NULL, &parents, "parent",
> > + N_("id of a parent commit object"), PARSE_OPT_NONEG,
>
> Comparing to other similar places, a single tab should be used to
> align "N_" instead of two spaces.I've seen a mix of both conventions scattered around, and wasn't sure which to stick to. I'll switch to that.
Thanks for your comments :-)