From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Marc Strapetz <marc.strapetz@syntevo.com>
Cc: git@vger.kernel.org
Subject: Re: Should update-index --refresh force writing the index in case of racy timestamps?
Date: Fri, 17 Dec 2021 21:14:22 +0000 [thread overview]
Message-ID: <Ybz9ruQ/uOfFbn3W@camp.crustytoothpaste.net> (raw)
In-Reply-To: <d3dd805c-7c1d-30a9-6574-a7bfcb7fc013@syntevo.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On 2021-12-17 at 10:44:32, Marc Strapetz wrote:
> For one of my Git-LFS test repositories, switching between branches quite
> often results in lots of racy index timestamps. Subsequent calls to "git
> update-index --refresh" or "git status" will invoke the "lfs" filter over
> and over again, just to figure out that all entries are still up-to-date.
> Hence, the index will never be rewritten and racy timestamps will remain.
>
> To break out of this state, it seems favorable to write the index if any
> racy timestamp is detected. We will be able to provide a patch if this
> change sounds reasonable.
Sure, this sounds reasonable, especially if, as you mentioned, git
status already does this. We might as well make the plumbing commands
as functional as the porcelain commands.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2021-12-17 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 10:44 Should update-index --refresh force writing the index in case of racy timestamps? Marc Strapetz
2021-12-17 11:04 ` Marc Strapetz
2021-12-17 21:14 ` brian m. carlson [this message]
2021-12-18 0:08 ` Junio C Hamano
2021-12-22 11:42 ` Marc Strapetz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ybz9ruQ/uOfFbn3W@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=marc.strapetz@syntevo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).