On Thu, Aug 29, 2013 at 3:03 PM, René Scharfe <l....@web.de> wrote:
> Am 29.08.2013 20:57, schrieb Felipe Contreras:
>> Matthieu Moy wrote:
>>> Felipe Contreras <felipe.contre...@gmail.com> writes:
>>>> Moreover, the --stage and --work
>>> --work alone sounds weird. At least to me, it does not immediately imply
>>> "working tree". It is tempting to call the option --work-tree, but git
>>> already has a global option with that name (git --work-tree=foo bar).
>> Yes, --work sounds weird, but so does --cherry. I thought about --wt, but
>> felt --work was more understandable, and --work-tree doesn't really give
>> more value, except more characters to type =/
> If you have a --work-tree option then parseopt accepts --work as well,
> unless it's ambiguous, i.e. another option starts with --work, too. So you
> can have a descriptive, extra-long option and type just a few characters at
> the same time.
Right, but what do we use in the documentation? Writing --work-tree in
the 'git reset' table for example would be rather ugly. I'm fine with
--work-tree, but I think it would be weird to have short-hands in the
documentation, although not entirely bad.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html