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

Re: Stack overflow at write_one()

From
Shawn Pearce <spearce@spearce.org>
Date
Nov 19, 2011, 23:30 UTC
Message-ID
<CAJo=hJv2aGEFcMjTPxJsyLerqUn3w3hc3hWnc1ScaDrSGihzyQ@mail.gmail.com>
In-Reply-To
<4EC823A0.3010603@cesarb.net>
On Sat, Nov 19, 2011 at 13:46, Cesar Eduardo Barros <cesarb@cesarb.net> wrote:
Show 7 quoted lines
> Em 19-11-2011 19:08, Junio C Hamano escreveu:
>>
>> Already found the real cause (jGit bug) and workaround posted, I think.
>
> I presume the cause then is what was fixed by
> http://egit.eclipse.org/w/?p=jgit.git;a=commit;h=2fbf296fda205446eac11a13abd4fcdb182f28d9
> ?

Yes. The AOSP servers were all updated with the above JGit patch, so the servers are no longer sending duplicate objects. But yes, for a period of time there were duplicates in the kernel repositories, particularly kernal/omap.

Previous: Cesar Eduardo BarrosNext: Cesar Eduardo Barros
Message 4 of 6 in “Stack overflow at write_one()”
  1. Cesar Eduardo BarrosNov 19, 2011
  2. Junio C HamanoNov 19, 2011
  3. Cesar Eduardo BarrosNov 19, 2011
  4. Shawn PearceNov 19, 2011
  5. Cesar Eduardo BarrosNov 20, 2011
  6. Shawn PearceNov 20, 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.