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

[BUG?] gc and impatience

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 3, 2013, 01:48 UTC
Message-ID
<CALkWK0k2B5OW9zMrw0jBDDWpufojYDJybXa7jCBdzftNUc7mxA@mail.gmail.com>
Hi,
I was pulling in some changes in the morning to find:
 Auto packing the repository for optimum performance. You may also
 run "git gc" manually. See "git help gc" for more information.

Being my usual impatient self, I opened another prompt and started merging changes. After the checkout, it started running another gc (why!?), which I attempted to kill using ^C.

  Counting objects: 449291   x$

It didn't just fail to stop, but it kept writing output making my prompt completely unusable. I finally just killed the pane. Now, it's struggling to update-index and update my cache (read: more waiting).

Why is gc not designed for impatient people, and what needs to be done to change this?

Ram
Next: Duy Nguyen
Message 1 of 7 in “[BUG?] gc and impatience”
  1. Ramkumar RamachandraAug 3, 2013
  2. Duy NguyenAug 3, 2013
  3. Junio C HamanoAug 3, 2013
  4. Duy NguyenAug 3, 2013
  5. Junio C HamanoAug 5, 2013
  6. Ramkumar RamachandraAug 5, 2013
  7. Ramkumar RamachandraAug 6, 2013

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.