git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Making it possible to do “git push origin” instead of “git push origin <branch>”, without having to one-time prepare each branch for it

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 22, 2016, 21:41 UTC
Message-ID
<xmqq7f6rfxpe.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAJtFkWtjowyGaFfsCVd-HAZM2-3e0=CkkyYfxne8KRdYq5kJ9g@mail.gmail.com>
Stefan Monov <logixoul@gmail.com> writes:
Show 12 quoted lines
> I'd like to use just:
>
>     git push
>
> or at most:
>
>     git push origin
>
> rather than having to first check which is the active branch with `git
> branch --list`, then type:
>
>     git push origin <branch>
Perhaps you are a target audience of
    $ git config push.default current
then?
Previous: Stefan MonovNext: Jacob Keller
Message 3 of 5 in “Making it possible to do “git push origin” instead of “git push origin <branch>”, without having to one-time prepare each branch for it”
  1. Stefan MonovDec 22, 2016
  2. Stefan MonovDec 22, 2016
  3. Junio C HamanoDec 22, 2016
  4. Jacob KellerDec 22, 2016
  5. Stefan MonovDec 27, 2016

Read the whole thread, see it on lore, or plain text.

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