Re: [PATCH v2] lockfile: add PID file for debugging stale locks
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 18, 2025, 01:33 UTC
- Message-ID
- <xmqq7bukzi8j.fsf@gitster.g>
- In-Reply-To
- <xmqqbjjwzkd4.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 8 quoted lines
> As this is about lockfile, you need to decide what should happen > when an older version of Git, which is unaware of this new world > order where .git/index.pid.lock declares ".git/index is being > updated; you should not touch it!", comes to the repository. You, > as a user of the updated Git, do want them to stop interferring with > the operation on the repository your new Git is making, and it means > you should have some way to telling them "do not touch---you do not > even understand what is in this repository!".
Ah, sorry, I take this back. We are not replacing index.lock with something else; we are adding index.pid.lock in addition; older versions of Git would simply ignore the new file, still notice index.lock and stop. So no need for extensions, either.