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

Re: [BUG] pull faulty 'not uptodate'

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 20, 2008, 21:22 UTC
Message-ID
<7v7iabpejv.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1508D1DF-EDE7-4A64-B354-E2F26578E24D@ai.rug.nl>
Pieter de Bie <pdebie@ai.rug.nl> writes:
> I think git pull does not refresh the index before trying to merge:
Yeah, that is another regression from C rewrite.  Thanks for reporting.

But I also have to wonder why a git-list regular like you are reporting this _long after_ v1.6.0-rc1 was released. Perhaps this is not really a big-deal bug spelled in capital letters like you have on your Subject line?

Previous: Pieter de BieNext: Pieter de Bie
Message 2 of 7 in “[BUG] pull faulty 'not uptodate'”
  1. Pieter de BieAug 20, 2008
  2. Junio C HamanoAug 20, 2008
  3. Pieter de BieAug 20, 2008
  4. Junio C HamanoAug 20, 2008
  5. Junio C HamanoAug 20, 2008
  6. "git-merge": allow fast-forwarding in a stat-dirty treeJunio C Hamano, Aug 20, 2008
  7. Miklos VajnaAug 20, 2008

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.