From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 18 Mar 2011 08:22:20 GMT
Subject: Re: [PATCH/RFD 0/2] revision.c: --merges, --no-merges and --merges-only
Message-ID: <7vbp18yh1f.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4D831043.1060709@drmicha.warpmail.net>

Michael J Gruber <git@drmicha.warpmail.net> writes:

> From the ui perspective I'm somehow not a big fan of tri-state options
> but can't give hard reasons why; maybe because they force you to use
> option arguments.

But in this particular case, you cannot really hack it with two options
that appear independent on surface but in reality are not. Logically, it
is an enum <everything, non-merges, merges-only> and you can choose only
one of them, and it is even worse from the UI perspective to use
combination of two not-quite-independent options.

Also I have a hidden agenda to add "because we could" --show=octopus to
the enum later perhaps only to my private edition ;-)