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

Re: git-rm -n leaves .git/index.lock if not allowed to finish

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Dec 19, 2008, 03:47 UTC
Message-ID
<20081219034757.GC21154@genesis.frugalware.org>
In-Reply-To
<7v63lhf1cl.fsf@gitster.siamese.dyndns.org>
On Thu, Dec 18, 2008 at 04:35:54PM -0800, Junio C Hamano <gitster@pobox.com> wrote:
> I think you need to have tons of files to cause the pipe buffer to fill up
> with the "rm 'frotz'" output, triggering a SIGPIPE to kill the upstream
> process of the pipe.

Ah, you are right. I did exactly what is in the lockfile.c part of your patch, but I did not think about "if I don't get a SIGPIPE for 2 lines, I may get one for 1000 lines". ;-)

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 6 in “git-rm -n leaves .git/index.lock if not allowed to finish”
  1. jidanni@jidanni.orgDec 18, 2008
  2. Miklos VajnaDec 19, 2008
  3. Junio C HamanoDec 19, 2008
  4. Miklos VajnaDec 19, 2008
  5. Junio C HamanoDec 19, 2008
  6. Junio C HamanoDec 19, 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.