On Fri, Aug 14, 2015 at 4:45 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Dave Borowitz <dborowitz@xxxxxxxxxx> writes: > >> On Fri, Aug 14, 2015 at 2:12 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >>> Yes, it looks somewhat strange. >> ... The straw-man >> strangeness is that two of them are the traditional boolean values >> "true/false" and the third is "file not found^W^W^Wif-possible" :) > > It actually is not uncommon for a Git configuration variable to > start its life as a boolean and then later become tristate (or more) > as we gain experience with the system, so don't worry about it being > "strange". A tristate, among whose choices two of them are true and > false, is not "strange" around here. Ok, so let us bikeshed a bit further. Bikeshed 1. Option A: --signed/--no-signed--signed-if-possible Option B: --signed=true|false|if-possible, "--signed" alone implies "=true". Bikeshed 2. Option A: if-possible The possibly confusing thing is one might interpret missing "gpg" to mean "impossible", i.e. "if gpg is not installed don't attempt to sign", which is not the behavior we want. I don't have another succinct way of saying this. "if-server-supported" is a mouthful. I think Jonathan mentioned "opportunistic", which is fairly opaque. > By "strange", I was referring to the possible perception issue on > having a choice other than yes/no for a configuration that allows > you to express your security preference. > > Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html