Re: git push default behaviour?

[Junio C Hamano <gitster@pobox.com>]

Junio C Hamano <gitster@pobox.com> writes:

> I just dug it up; start from here:
>
>     http://thread.gmane.org/gmane.comp.version-control.git/123350/focus=123541
>
> read on a few messages downthread, and then jump to the other thread
> Nana points at in the above message.
>
> In short, we started warning that we _might_ change the default
> someday, without having a clear concensus or plan, that ended up
> confusing and annoying users without giving them anything good,
> other than awareness that such a feature is _available_.
>
> So no, the conversation did not decide if changing the default was
> warranted or not. It just confirmed that we weren't anywhere close
> to deciding back then.

I think MJG's message (the second on in the "git push origin error"
thread) is probably what we would need to repeat, and this time more
strongly to squelch the opposition from old timers, if somebody
wants to resurrect the "warn until you set the default explicitly,
intending to change the default in the future" patch. And this time
around, the plan to change the default should be more concrete with
specific date, e.g. "Starting from April 1st, 2013".

I was in the "keep the default to matching, so that nobody among
existing 47 million users would be annoyed" camp (back then we
probably didn't have 47 million users, but that is besides the
point) and I still am, but notice that I was defending the argument
by the "let's be ( (new user) friendly )" camp in that thread. And
without much fire-support from those who were vocal about it.

Re-reading the thread made me sick.

I wish I had enough energy remaining to say "Let's try one more
time, and hope that people from the 'let's change the default' camp
will behave much better than the last time", but I do not have high
hopes, after having been burned once already with exactly the same
issue.