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

Re: [bug] pull faulty 'not uptodate'

From
PBPieter de Bie <pdebie@ai.rug.nl>
Date
Aug 20, 2008, 21:29 UTC
Message-ID
<EAFC48F0-5512-4A83-B9B2-44FF53319285@ai.rug.nl>
In-Reply-To
<7v7iabpejv.fsf@gitster.siamese.dyndns.org>
On Aug 20, 2008, at 11:22 PM, Junio C Hamano wrote:
Show 6 quoted lines
> 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?

I just noticed it and wanted to report it. I thought the usual way to do this is to put [BUG] in the subject line. If that is not the common way to report bugs, I'm sorry. I can also downcase it ;)

- Pieter
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.