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

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Mar 16, 2012, 12:42 UTC
Message-ID: <vpqhaxohg3n.fsf@bauges.imag.fr>
In-Reply-To: <7vy5r0iwdb.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 8 quoted lines

> 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?

I meant just push the current one to its own name.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.