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

error: addinfo_cache failed during merge

From
SBStephen Bash <bash@genarts.com>
Date
Sep 28, 2011, 14:44 UTC
Message-ID
<26411548.33530.1317221043429.JavaMail.root@mail.hq.genarts.com>
In-Reply-To
<8172019.33448.1317219409234.JavaMail.root@mail.hq.genarts.com>
Hi all-
I'm in the process of implementing whitespace and EOL normalization for our repo.  Having completed the work on our oldest maintenance branch, I'm attempting to merge the changes recursively into newer branches.
My approach is to merge using '-s recursive -X ours --no-commit' since the only conflicts are whitespace/EOL changes and I have to renormalize the current branch before committing anyway (new files, etc.).  Unfortunately, during the merge, I got a bunch of errors like this:
error: addinfo_cache failed for path 'foo/bar.h'
So first, is this important?  Second, can that message be replaced with something more helpful?  I'm not exactly a newbie, and I certainly can't grok that message...
Doing a bit of archeology, pickaxe shows it arose in 0424138 "Fix bogus error message from merge-recursive error path", but that was Junio cleaning up the message a bit.  The original message is from the creation of merge-recursive.c in 6d297f8 "Status update on merge-recursive in C".  I should caveat that my local git/git is a little out of date because I haven't repointed it since k.org went down (I use it very rarely), so there might be something newer in this area.

Thanks, Stephen

Next: Junio C Hamano
Message 1 of 5 in “error: addinfo_cache failed during merge”
  1. Stephen BashSep 28, 2011
  2. Junio C HamanoSep 28, 2011
  3. Stephen BashSep 28, 2011
  4. Stephen BashSep 28, 2011
  5. Stephen BashSep 28, 2011

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.