Thread (5 messages) 5 messages, 3 authors, 2016-06-15

Re: Why does 'submodule add' stage the relevant portions?

From: Ramkumar Ramachandra <hidden>
Date: 2016-06-15 22:56:31

Junio C Hamano wrote:
Ramkumar Ramachandra [off-list ref] writes:
quoted
I'm talking about slightly better defaults at the porcelain level,
at most.
If a change does not even have to break backward compatibilty, that
is a regular enhancement and independent from 2.0, no?
Okay, I'm confused: why are you waiting for 2.0 to change push.default
then?  Isn't that just a "slightly better default at the porcelain
level" and hence a "regular enhancement"?

You're not worried about breaking everyone's muscle memory (is that
not part of backward compatibility)?  So, if I understand correctly, I
can do changes like the following at any time (provided the reviewers
agree that they're sane):
1. Don't make 'git submodule add' stage (which is what this thread was
originally about).
2. Set pull.autostash to true (I still have to re-roll and finish it ofcourse).
3. Set color.ui to auto.
4. Alias 'git status' to 'git status -sb'.
5. Set help.autocorrect to 20.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help