Re: [PATCH 4/4] archive: use parseopt for local-only options
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 8, 2009, 20:20 UTC
- Message-ID
- <7v3adnlqby.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <49B40CC1.2090906@lsrfire.ath.cx>
René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> The parseopt parser allows multiple occurrences of --remote and --exec > unlike the previous one; the one specified last wins. This looseness > is acceptable, I think.
I agree.
If we care about this very deeply, we can add "this option is supposed to be singleton" option to the parse_options infrastructure. Besides, the "last one wins" rule is often more convenient than "there has to be at most one" rule in real life.