(off-list ancestor, not in this archive)
Re* [1.8.0] Provide proper remote ref namespaces · Junio C Hamano <hidden> · 2016-06-15
Re: Re* [1.8.0] Provide proper remote ref namespaces · Jay Soffian <hidden> · 2016-06-15
Re: Re* [1.8.0] Provide proper remote ref namespaces · Sverre Rabbelier <hidden> · 2016-06-15
Re: Re* [1.8.0] Provide proper remote ref namespaces · Jay Soffian <hidden> · 2016-06-15
Re: [1.8.0 RFC] push: start warning upcoming default change for push.default · Jonathan Nieder <hidden> · 2016-06-15
Re: [1.8.0 RFC] push: start warning upcoming default change for push.default · Jay Soffian <hidden> · 2016-06-15
Re: [1.8.0 RFC] push: start warning upcoming default change for push.default · Jonathan Nieder <hidden> · 2016-06-15
Re: Re* [1.8.0] Provide proper remote ref namespaces · Johan Herland <hidden> · 2016-06-15

Re: [1.8.0 RFC] push: start warning upcoming default change for push.default

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:50:33

Possibly related (same subject, not in this thread)

2016-06-15 · Re: [1.8.0 RFC] push: start warning upcoming default change for push.default · Jonathan Nieder <hidden>

Jay Soffian wrote:

If everyone
sets push.default to 'matching' because that's what the message
advises, what's the point of changing the implicit default to
'current'?

That new installations after v1.8.0 would use the more sensible behavior?