From: Christoph Groth <christoph@grothesque.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Stat cache in .git/index hinders syncing of repositories
Date: Sat, 18 Jan 2020 20:06:21 +0100 [thread overview]
Message-ID: <87pnfgshxu.fsf@drac> (raw)
In-Reply-To: <xmqq7e1od41x.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Sat, 18 Jan 2020 10:15:22 -0800")
Junio C Hamano wrote:
> Christoph Groth <christoph@grothesque.org> writes:
>
> > However, there is one problem with syncing git repositories, that
> > has been noticed by multiple people [1]: The file .git/index
> > contains not only the “git index”, but also a cache of stat-data of
> > the files in the working directory. Some file synchronizers are
> > able to sync mtimes, but syncing ctimes would be bizarre (if it is
> > even possible).
>
> The stat-data in the index file is meant to be a mere optimization,
> and after copying .git/index and the working tree files to a new box,
> running "git update-index --refresh" would make them in sync, no?
Let’s assume that one somehow manages to teach the synchronizer to run
"git update-index --refresh" immediately after copying the index file
and to consider the resulting modified .git/index file as identical to
the version on the other side. (That would be already really difficult,
because it’s against the design of synchronizers to consider differing
files to be identical.)
Even then, .git/index will change again whenever the mtime of any
tracked file changes. That can easily happen through "touch" or
modifying a file and then reverting the change. There’s no way for the
synchronizer to tell the difference between relevant and irrelevant
changes to .git/index. (Short of writing a specialized tool for
comparing git index files and embedding it.)
Would it be feasible to move this optimization data to a separate file
without breaking backwards and forwards compatibility? I guess it
would: the data format of .git/index could remain identical, but newer
versions of git could ignore the stat data in the index file and use
a separate file for that. If an older version of git is used with the
repository, it would simply notice that the stat data in .git/index is
not up-to-date.
But if the above is not feasible for some reason, would it be possible
to provide a switch for disabling stat caching optimization?
I believe that synchronizing files between machines is something that
will become ever more important with new tools like syncthing. So it
would be really cool if git were to support such usage. It *almost*
does!
next prev parent reply other threads:[~2020-01-18 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 23:57 Stat cache in .git/index hinders syncing of repositories Christoph Groth
2020-01-18 18:15 ` Junio C Hamano
2020-01-18 19:06 ` Christoph Groth [this message]
2020-01-18 19:42 ` brian m. carlson
2020-01-18 22:04 ` Christoph Groth
2020-01-20 12:01 ` Johannes Schindelin
2020-01-20 23:53 ` Christoph Groth
2020-01-21 2:53 ` brian m. carlson
2020-01-24 9:16 ` Christoph Groth
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnfgshxu.fsf@drac \
--to=christoph@grothesque.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).