From: "Torsten Bögershausen" <tboegi@web.de>
To: Patrick Hemmer <git@stormcloud9.net>, git@vger.kernel.org
Subject: Re: Set file modification time on checkout
Date: Thu, 13 Nov 2014 06:04:15 +0100 [thread overview]
Message-ID: <54643BCF.5000900@web.de> (raw)
In-Reply-To: <54643780.7060504@stormcloud9.net>
On 2014-11-13 05.45, Patrick Hemmer wrote:
> The request is to allow git to set the file modification time on
> checkout to the commit-author-date of the commit which last modified the
> file.
> Yes I know this is in the FAQ, but the FAQ entry is missing an
> increasingly common use case: docker.
> When docker builds an image, it generates layers of images based on each
> build step. Adding a file would be a build step, and for this action it
> generates a hash based on the file modification time & content.
Why do they do this?
The file content is the only thing that matters.
The other thing is to use a hook, utilizing test-chmtime
from test-chmtime.c
prev parent reply other threads:[~2014-11-13 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 4:45 Set file modification time on checkout Patrick Hemmer
2014-11-13 5:04 ` Torsten Bögershausen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54643BCF.5000900@web.de \
--to=tboegi@web.de \
--cc=git@stormcloud9.net \
--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.
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).