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

Re: Push and remote refs

From
Junio C Hamano <junkio@cox.net>
Date
Nov 5, 2006, 19:37 UTC
Message-ID
<7vhcxdu1ln.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0611051333210.9789@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
Show 5 quoted lines
> Usually, I use the same computer to do this multiple times in a row, and 
> it's a bit inconvenient that, after pushing local "for-mainline" to remote 
> "master", I have to fetch remote "master" to local "mainline". It would be 
> nice if git would update local tracking of remote refs when it pushes to 
> those remote refs.

I recall discussing this exact behaviour with Pasky when he added it to Cogito. I think we concluded that it is a very sensible thing to pretend we fetched immediately after we successfully pushed and got the same thing back, and there is no risk of data loss or user confusion, as long as we catch failure from the push and refrain from doing this update, which Cogito did implement correctly when we discussed this.

Previous: Daniel BarkalowNext: Jeff King
Message 2 of 5 in “Push and remote refs”
  1. Daniel BarkalowNov 5, 2006
  2. Junio C HamanoNov 5, 2006
  3. Jeff KingNov 5, 2006
  4. Junio C HamanoNov 5, 2006
  5. Jeff KingNov 5, 2006

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.