Re: [RFC PATCH] push: start warning upcoming default change for push.default
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 16, 2012, 12:05 UTC
- Message-ID
- <7vy5r0iwdb.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <vpq1uosswwz.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> I'd count "upstream is not set" as "current and upstream agree on > 'current'". IOW, use "current", but error out if there's a configured > upstream that is different.
And if there is no configured upstream, should it error out, or should it just push the current one to its own name?