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

Re: Diagnosing stray/stale .keep files -- explore what is in a pack?

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 15, 2014, 17:49 UTC
Message-ID
<xmqqr4892l0u.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CACPiFCKeOYHUb22d_Ea0PcbU-uAn=fVAn0QP1qbLAiNh1KEoqQ@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail.com> writes:
Show 6 quoted lines
> On Wed, Jan 15, 2014 at 4:12 AM, Jeff King <peff@peff.net> wrote:
>> We see these occasionally at GitHub, too. I haven't yet figured out a
>> definite cause, though whatever it is, it's relatively rare.
>
> Do you have a cleanup script to safely get rid of stale .keep and
> .lock files? I wonder what other stale bits merit a cleanup...

As long as we can reliably determine that it is safe to do so without risking races, automatically cleaning .lock files is a good thing to do.

Cleaning .keep files needs the same care and a bit more, though. You of course have to be sure that no other concurrent process is in the middle of doing something, but you also need to be sure that the ".keep" file is not a marker created by the end user to say "keep this pack, do not subject its contents to repacking" after a careful repacking of the stable part of the history.

Previous: Martin LanghoffNext: Martin Langhoff
Message 7 of 10 in “Diagnosing stray/stale .keep files -- explore what is in a pack?”
  1. Martin LanghoffJan 14, 2014
  2. Martin LanghoffJan 14, 2014
  3. Martin FickJan 14, 2014
  4. Martin LanghoffJan 14, 2014
  5. Jeff KingJan 15, 2014
  6. Martin LanghoffJan 15, 2014
  7. Junio C HamanoJan 15, 2014
  8. Martin LanghoffJan 15, 2014
  9. Duy NguyenJan 16, 2014
  10. Jeff KingJan 21, 2014

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.