Re: push.default: current vs upstream

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Apr 12, 2012, 08:09 UTC
Message-ID: <vpqhawp2wxs.fsf@bauges.imag.fr>
In-Reply-To: <20120412075535.GC31122@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> I think it is as simple as applying the usual upstream rules, then
> checking the remote name against the local name. Like this:

This fails if no upstream is configured. I think applying "current" instead of failing in this case makes perfect sense (i.e. "simple" should fail only if there is an upstream configured, and it has a different 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.