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

Re: [PATCH 2/3] push: add --current

From
Paolo Bonzini <paolo.bonzini@gmail.com>
Date
Jul 20, 2009, 09:48 UTC
Message-ID
<4A643D7B.9090900@gmail.com>
In-Reply-To
<20090720071413.GA29915@atjola.homenet>
Show 9 quoted lines
>> +--current::
>> +	Independent of the other options, restrict pushing to the current
>> +	HEAD.
>
> To me, this sounds like there are multiple HEADs and this selects the
> current one to be pushed, which would be wrong. Maybe this could be
> written as:
>
> 	Restrict pushing to the currently checked out branch head.

I wrote that referring to "the branch currently pointed to by [the symref] HEAD".

> Hm, this only talks about refspecs in the config, but your patch series
> is especially about push.default=tracking, which is not a refspec set in
> the config, but causes a refspec to be generated on the fly.

Not really, as push.default=tracking and push.default=current would anyway push only the currently checked out branch. "git push --current" would have a visible effect only for push.default=matching (the effect would be the same as push.default=current except that a new branch will not be created remotely).

If you have creted all your tracking branches with autosetuppush, then in that case "git push --current" or pushHeadOnly will indeed achieve the same effect as push.default=tracking; however, that would be with real refspecs in the config rather than with one generated on the fly. And since in that case you have a push refspec in the configuration, push.default would not be used.

Paolo
Previous: Björn SteinbrinkNext: Tay Ray Chuan
Message 5 of 9 in “add push --current and remote.*.pushHeadOnly”
  1. 0/3 add push --current and remote.*.pushHeadOnlyPaolo Bonzini, Jul 20, 2009
  2. 1/3 reintroduce PUSH_DEFAULT_UNSPECIFIEDPaolo Bonzini, Jul 20, 2009
  3. 2/3 push: add --currentPaolo Bonzini, Jul 20, 2009
  4. Björn SteinbrinkJul 20, 2009
  5. Paolo BonziniJul 20, 2009
  6. Tay Ray ChuanJul 20, 2009
  7. Paolo BonziniJul 20, 2009
  8. demerphqJul 20, 2009
  9. 3/3 push: add remote.*.pushHeadOnly configurationPaolo Bonzini, Jul 20, 2009

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.