Re: [PATCH v3] Add core.mode configuration

Krzysztof Mazur wrote:

On Sat, Oct 12, 2013 at 02:04:45AM -0500, Felipe Contreras wrote:

quoted

So that we can specify general modes of operation, specifically, add the
'next' mode, which makes Git pre v2.0 behave as Git v2.0.

Signed-off-by: Felipe Contreras <redacted>
---

I don't think that single option it's a good idea. From the user's
point of view I think that the way push.default was introduced and
will be changed is much better. So maybe it's better to just add
"core.addremove" option instead?

Maybe, but what happens when we start doing changes for v3.0? As a user, I
don't and to figure out which are the new configurations that will turn v3.0
behavior on, I just want to be testing that mode, even if I'm not following Git
development closely. If I find something annoying with core.mode = next, I
report the problem to the mailing list, which is good, we want to know problems
with the backward-incompatible changes that will be introduced before it's too
late, don't we?

I'd be fine with having *both* a fine-tuned option to trigger each specific
behavior, and another one that turns all those fine-tuned options on that are
meant for v2.0.

Unfortunately, I don't see much interest from Git developers in either.

-- 
Felipe Contreras