Re: [PATCH 4/3] parse-options: disallow --no-no-sth
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 28, 2012, 21:15 UTC
- Message-ID
- <7vlinmy80x.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <4F4D3545.6060704@lsrfire.ath.cx>
René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> Now that options whose definition starts with "no-" can be negated > by removing said "no-", there is no need anymore to allow them to > be negated by adding a second "no-", which just looks silly.
Thanks. But accepting them silently and do what the user would have expected, especially if we do not advertise it, would not hurt anybody, no?