Jeff King <peff@xxxxxxxx> writes:
> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html