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

Re: [BUG?] gc and impatience

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 5, 2013, 15:24 UTC
Message-ID
<7vk3k0not6.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8DO4VyCK_xDJDGVx6JLTqjKAf24AUOW3=kZEMEVjAUSVw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
> I worry less about this. It's not the right model to have two machines
> modify the same shared repository (gc --auto is only triggered when we
> think there are new objects) even though I think we support it.

I am a bit hesitant to dismiss with "It's not the right model", as the original of accessing the repository from two terminals while one clearly is being accessed busily by gc falls into the same category.

> If
> it's two _scripts_ modifying the same repo, I don't care as this is
> more about user interaction.

It can very well be two terminals, one on one machine each, both with the same human end-user interaction.

Previous: Duy NguyenNext: Ramkumar Ramachandra
Message 5 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.