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

Re: [External] Re: [PATCH v2] read-cache: report lock error when refreshing index

From
Han Young <hanyang.tony@bytedance.com>
Date
Jul 8, 2025, 02:47 UTC
Message-ID
<CAG1j3zFz0RQ3mf=BRAQhCDWucOR0J9Z26Wmmz8G6+9dMbNO3Ag@mail.gmail.com>
In-Reply-To
<xmqq8qkz5193.fsf@gitster.g>
On Tue, Jul 8, 2025 at 2:01 AM Junio C Hamano <gitster@pobox.com> wrote:
> No need to resend, as I've done so locally while applying.
Thank you, I'll be careful next time.
Previous: Junio C Hamano
Message 6 of 6 in “read-cache: report lock error when refreshing index”
  1. read-cache: report lock error when refreshing indexHan Young, Jul 1, 2025
  2. Justin ToblerJul 1, 2025
  3. Junio C HamanoJul 1, 2025
  4. read-cache: report lock error when refreshing indexHan Young, Jul 3, 2025
  5. Junio C HamanoJul 7, 2025
  6. Han YoungJul 8, 2025

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.