From: Junio C Hamano <gitster@pobox.com>
To: Fabrizio Pollastri <f.pollastri@inrim.it>
Cc: git@vger.kernel.org
Subject: Re: preserving mtime
Date: Fri, 16 Nov 2007 02:21:36 -0800 [thread overview]
Message-ID: <7v1waqze1b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <473D63F9.4010201@inrim.it> (Fabrizio Pollastri's message of "Fri, 16 Nov 2007 10:33:45 +0100")
Fabrizio Pollastri <f.pollastri@inrim.it> writes:
> is it possible to tell git to preserve the file modification time in a
> checked out copy? It is useful when managing web files, where mtime is
> tested by spiders for download decisions.
"git checkout branchA" after "git checkout branchB" would not
touch "file" if "file" are identical between two branches, so
the modification time is already preserved.
If the contents of "file" from the version you would want to
check out is different from the version you previously checked
out, and you still want to keep the old timestamp, then you are
trying to do something that a normal SCM user would actively not
want (e.g. doing so would screw up the build systems such as
"make"). Such a specialized need usually is addressed by the
build and install procedure of the application (in your case, a
website management). Maybe your current build procedure may
blindly copy when installing:
install: web.html
$(install) web.html $(dest)/var/www/web.html
but you may want to ignore certain classes of changes and avoid
re-installing to help crawlers. You would do:
install = ./myinstall.sh
install: web.html
$(install) web.html $(dest)/var/www/web.html
and then ./myinstall.sh might look like:
#!/bin/sh
test -f "$2" &&
compare-ignoring-minor-changes "$1" "$2" && exit 0
install "$1" "$2"
next prev parent reply other threads:[~2007-11-16 10:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 9:33 preserving mtime Fabrizio Pollastri
2007-11-16 10:15 ` Andreas Ericsson
2007-11-17 18:22 ` Wayne Davison
2007-11-18 8:45 ` Mike Hommey
2007-11-18 9:34 ` Martin Langhoff
2007-11-18 18:47 ` David Brown
2007-11-18 20:36 ` Martin Langhoff
2007-11-18 21:44 ` David Brown
2007-11-18 9:40 ` Jan Hudec
2007-11-18 10:42 ` Robin Rosenberg
2007-11-19 14:38 ` Johannes Schindelin
2007-11-16 10:19 ` Jakub Narebski
2007-11-16 10:21 ` Junio C Hamano [this message]
2007-11-16 12:09 ` Erik Warendorph
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=7v1waqze1b.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=f.pollastri@inrim.it \
--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).