From: David Brown <git@davidb.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Mike Hommey <mh@glandium.org>,
Wayne Davison <wayne@opencoder.net>, Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org
Subject: Re: preserving mtime
Date: Sun, 18 Nov 2007 10:47:24 -0800 [thread overview]
Message-ID: <20071118184724.GA494@old.davidb.org> (raw)
In-Reply-To: <46a038f90711180134j411bb9c9uf2476f564f9abb6@mail.gmail.com>
On Sun, Nov 18, 2007 at 10:34:55PM +1300, Martin Langhoff wrote:
>I do hope anyone doing those things is _very_ aware that the mtime
>metadata has a specific meaning -- when did this specific file in this
>filesystem last change -- and is used by many tools in that sense. You
>are trying to use it for something else. Lots of things will break.
>
>Like incremental backups, for example.
'mtime' does _not_ have the specific meaning of 'when did this specific
file last change'. That is the 'ctime' field. 'mtime' is also updated
when a file is modified, but can be changed by the user. Many utilities
restore mtime to older values, including tar.
Any competent backup program would use 'ctime' for incremental backups,
unless they don't mind missing a vast majority of files on many machines.
The main thing I've seen mess up backup software is if the mtime is set
into the future.
However, it will make 'make' very confusing, since it uses the mtime to
determine if files are out of date. If moving to an older version of a
file causes the file to become older, make won't recompile. This is
arguably a defect in make, but that is how it works.
Preserving mtime definitely should not be a default.
David
next prev parent reply other threads:[~2007-11-18 18:47 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 [this message]
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
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=20071118184724.GA494@old.davidb.org \
--to=git@davidb.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=mh@glandium.org \
--cc=wayne@opencoder.net \
/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).