From: Daniel Fanjul <daniel.fanjul.alcuten@gmail.com>
To: git-users@googlegroups.com
Cc: Git List <git@vger.kernel.org>
Subject: Re: [git-users] git checkout file with custom mtime
Date: Wed, 9 Jan 2019 23:57:08 +0100 [thread overview]
Message-ID: <CAPktr3kR521rw1n0Sw-q-gkHQrc3wwLyhSo=aubrDTT3-sLhUQ@mail.gmail.com> (raw)
In-Reply-To: <20190109162045.4mit42qvnz6fpb3j@tigra>
The mtime of the files in my working copy change when I amend or
rebase or checkout different branches or in general when I use git
commands. I carefully store the mtime when these files are generated
or overwritten and restore it when it is going to be read. The tool I
use is https://packages.ubuntu.com/bionic/metastore and does not have
stale information.
I do not know how git lfs will work here, it handles large contents
but I doubt it will handle the mtimes as I need.
prev parent reply other threads:[~2019-01-09 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <951cafaa-877b-4815-862f-5ffc43e6976a@googlegroups.com>
2019-01-05 20:35 ` [git-users] git checkout file with custom mtime Philip Oakley
2019-01-05 21:44 ` Daniel Fanjul
2019-01-09 16:20 ` Konstantin Khomoutov
2019-01-09 22:57 ` Daniel Fanjul [this message]
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='CAPktr3kR521rw1n0Sw-q-gkHQrc3wwLyhSo=aubrDTT3-sLhUQ@mail.gmail.com' \
--to=daniel.fanjul.alcuten@gmail.com \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.org \
/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).