Re: git push default behaviour?

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 9, 2012, 05:23 UTC
Message-ID: <7vsjhi9wku.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120309033826.GA6164@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 9 quoted lines

> This is all sounding eerily familiar. Indeed:
>
>   $ git log --oneline -Swarn_unconfigured_push -- builtin-push.c
>   bba0fd2 push: do not give big warning when no preference is configured
>   665d3e8 Display warning for default git push with no push.default config
>
> I don't remember the mailing list conversations that surrounded those
> patches, but if we are going to have the same conversation again, maybe
> it is worth looking them up.

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.