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

Re: bug: origin refs updated too soon locally

From
PWPerry Wagle <wagle@cs.indiana.edu>
Date
Oct 18, 2007, 01:43 UTC
Message-ID
<8E28A8CC-DC3B-4C97-8B14-742DAA8D3CE2@cs.indiana.edu>
In-Reply-To
<8CEF6150-4BE7-4B4D-B58C-12CE4671007E@cs.indiana.edu>

I take it back. A git-pull is not a workaround if the ref moved on the remote end.

-- Perry
On Oct 17, 2007, at 6:35 PM, Perry Wagle wrote:
Show 11 quoted lines
> If I clone a remote repository, make a few commits, push them to  
> the remote repository, and the update hook on the remote repository  
> rejects them (exit 1), the local origin refs are still updated as  
> if the push had gone through.  The workaround is to do a pull to  
> set the origin refs back.
>
> -- Perry
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous: Perry WagleNext: Shawn O. Pearce
Message 2 of 8 in “bug: origin refs updated too soon locally”
  1. Perry WagleOct 18, 2007
  2. Perry WagleOct 18, 2007
  3. Shawn O. PearceOct 18, 2007
  4. Jeff KingOct 18, 2007
  5. t5516: test update of local refs on pushJeff King, Oct 18, 2007
  6. Jeff KingOct 18, 2007
  7. Shawn O. PearceOct 18, 2007
  8. 2/2 send-pack: don't update tracking refs on errorJeff King, Oct 18, 2007

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.