Daniel,

Do you use the Git LFS (Large File System) add-on?, are you on Windows or Linux?, and what tools need mtime (or is it something about the process of using the tool..)?

The Git viewpoint is that the mtime shouldn't be important for the version storage & control aspects, though it maybe for the external compiler tooling, so they do tend to try to keep the mtime/ctime consistent.

I'm not aware of specific capability to do what you ask, but it may be worth discussing this on the git mailing list "Git List <git@vger.kernel.org>" (which only accepts 100% plain text, no HTML, messages). The mailing list archive is at https://public-inbox.org/git/?q= where you can search for mtime/ctime discussions.

There will be a Git developer conference at the end of the month, so it is worth raining it soonish, even if it becomes an add on the fires via a post checkout hook that updates the mtimes from a stored file of 'true' mtimes (plus updates the index's view of those mtimes.

Philip

On 05/01/2019 13:33, Daniel Fanjul wrote:
Hi all,

I have some large files tracked in git and I have to track their mtime because of some legacy software. With another tool I save and restore their mtime. When I restore their mtime git status rereads the files to update the mtime in the index. I would like to improve that because there are too many files, the whole I/O is too slow and the whole process is triggered too often.

I would like a way to tell git to checkout a file and set a given mtime at the same time so the index is updated with the mtime but the file is not rewritten because the working copy is clean. This would solve my problem. Do you know a way to do this?

Do you know any other way to handle this properly?

Thanks in advance, and happy new year,
Daniel.
--
You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com <mailto:git-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

Reply via email to