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

Re: git pull fails

From
THTimo Hirvonen <tihirvon@gmail.com>
Date
Mar 29, 2006, 00:11 UTC
Message-ID
<20060329031136.e0389c00.tihirvon@gmail.com>
In-Reply-To
<20060328224807.GC27689@pasky.or.cz>
Petr Baudis <pasky@suse.cz> wrote:
> If I understand it right, Timo complains that git-fetch got
> non-fastforward commits for "pu" and "next" and a good fastforward
> commit for "master", but it didn't update the ref for ANY head, not even
> the "master".

Exactly. Maybe git-fetch should abort only if it could not update the currently checked out branch?

-- 
http://onion.dynserv.net/~timo/
Previous: Petr BaudisNext: Junio C Hamano
Message 6 of 10 in “git pull fails”
  1. Timo HirvonenMar 28, 2006
  2. Ralf BaechleMar 28, 2006
  3. Timo HirvonenMar 28, 2006
  4. Radoslaw SzkodzinskiMar 28, 2006
  5. Petr BaudisMar 28, 2006
  6. Timo HirvonenMar 29, 2006
  7. Junio C HamanoMar 29, 2006
  8. Petr BaudisMar 29, 2006
  9. Junio C HamanoMar 29, 2006
  10. Petr BaudisMar 29, 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.