From: Junio C Hamano Date: Fri, 16 Mar 2012 12:05:52 GMT Subject: Re: [RFC PATCH] push: start warning upcoming default change for push.default Message-ID: <7vy5r0iwdb.fsf@alter.siamese.dyndns.org> In-Reply-To: Matthieu Moy 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?