Thread (25 messages) flat view 25 messages, 5 authors, 2016-06-15

Re: [PATCH v3] Add core.mode configuration

From: John Szakmeister <hidden>
Date: 2016-06-15 22:59:00

On Tue, Oct 15, 2013 at 10:51 AM, Krzysztof Mazur [off-list ref] wrote:
On Tue, Oct 15, 2013 at 08:29:56AM -0500, Felipe Contreras wrote:
quoted
Krzysztof Mazur wrote:
quoted
On Tue, Oct 15, 2013 at 07:32:39AM -0500, Felipe Contreras wrote:
quoted
Krzysztof Mazur wrote:
quoted
But with core.mode = next after upgrade you may experience incompatible
change without any warning.
Yes, and that is actually what the user wants. I mean, why would the user set
core.mode=next, if the user doesn't want to experencie incompatible changes? A
user that sets this mode is expecting incompatible changes, and will be willing
to test them, and report back if there's any problem with them.
With your patch, because it's the only way to have 'git add' v2.0.
Yeah, but that's not what I'm suggesting. I suggested to have *both* a
fined-tunned way to have this behavior, say core.addremove = true, and a way to
enable *all* v2.0 behaviors (core.mode = next).
I'm just not sure if a lot of users would use core.mode=next, because
of possible different behavior without any warning. Maybe we should also
add core.mode=next-warn that changes defaults like next but keeps warnings
enabled until the user accepts that change by setting appropriate
config option? That's safer than next (at least for interactive use) and
maybe more users would use that, but I don't think that's worth adding.
I like the idea that we could kick git into a mode that applies the
behaviors we're talking about having in 2.0, but I'm concerned about
one aspect of it.  Not having these behaviors until 2.0 hits means
we're free to renege on our decisions in favor of something better, or
to pull out a bad idea.  But once we insert this knob, I don't know
that we have the same ability.  Once people realize it's there and
start using it, it gets harder to back out.  I guess we could maintain
the stance that "the features are not concrete yet," or something like
that, but I think people would still get upset if something changes
out from under them.

So, at the end of the day, I'm just not sure it's worthwhile to have.

-John
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help