Re: [RFC/PATCH] git push usability improvements and default change

From: Miles Bader <miles@gnu.org>
Date: Mar 12, 2009, 10:52 UTC
Message-ID: <buomybrqahe.fsf@dhlpc061.dev.necel.com>
In-Reply-To: <20090312102243.GA27665@pvv.org>

Finn Arne Gangstad <finnag@pvv.org> writes:

> The main problem with all these examples is that the underlying
> assumption is that you can always use the same branch name locally and
> remotely.

Presumably the push --track option would be used with an explicit branch name given to push anyway, right? Then it can use that info to set up the tracking flexibly (and with sane defaults).

E.g.,, simple case:

    git push --track SOME_REMOTE BRANCH_NAME

complex case:

    git push --track SOME_REMOTE MY-BRANCH:REMOTE-BRANCH

-Miles

-- 
=====
(^o^;
(()))
*This is the cute octopus virus, please copy it into your sig so it can spread.

$ 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.