From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Mike Hommey" <mh@glandium.org>
Cc: "Wayne Davison" <wayne@opencoder.net>,
"Andreas Ericsson" <ae@op5.se>,
git@vger.kernel.org
Subject: Re: preserving mtime
Date: Sun, 18 Nov 2007 22:34:55 +1300 [thread overview]
Message-ID: <46a038f90711180134j411bb9c9uf2476f564f9abb6@mail.gmail.com> (raw)
In-Reply-To: <20071118084511.GC16863@glandium.org>
On Nov 18, 2007 9:45 PM, Mike Hommey <mh@glandium.org> wrote:
> On Sat, Nov 17, 2007 at 10:22:36AM -0800, Wayne Davison wrote:
> > I wish that the initial clone would set the modification time to the
> > commit time. It would make the intial checkout have a more accurate
> > representation of when a file was last changed instead of all files
...
> For completeness, it would make sense to do so every time you git
> checkout (like, when switching branches).
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.
So no no NO. Not recommended. Stuff will break in new and surprising
ways. It'd be trivial to write a quick script that shows the data you
want from git in Perl/Python/etc. But don't use mtime. It's used for
other stuff. Actually used for other stuff. Don't replace that data
with time data you want to see, the actual users of mtime will break.
cheers,
m
next prev parent reply other threads:[~2007-11-18 9:35 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 [this message]
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
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=46a038f90711180134j411bb9c9uf2476f564f9abb6@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--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).