From: Peter Krefting <peter@softwolves.pp.se>
To: dhruva <dhruvakm@gmail.com>
Cc: jidanni@jidanni.org, Git Mailing List <git@vger.kernel.org>
Subject: Re: timestamps not git-cloned
Date: Fri, 28 Nov 2008 15:59:56 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0811281554560.14606@ds9.cixit.se> (raw)
In-Reply-To: <e3f230850811271908g1be6b3f9t3e678081088de06b@mail.gmail.com>
Hi!
dhruva:
> I do not think there is an VCS that records timestamps. Only file
> contents are tracked.
CVS sort of does. The initial checkout sets the time stamp of files to
their last *check-in* time (and you can import a file with -D to set
its commit time to the current timestamp). Updates do, however, set to
current time (to not break make and friends).
I miss this behaviour in Git, but I have learnt to live with it. I
guess it is like a difference in philosophy on what time-stamps are
supposed to record, like how UNIX "cp" sets the time of the new-born
copy to now, while DOS "copy" sets it to the old time-stamp. Coming
to Unix and Linux from DOS (via OS/2), I find "cp" behaviour weird. But
have learnt to live with it (and use "cp -a" a lot).
--
\\// Peter - http://www.softwolves.pp.se/
next prev parent reply other threads:[~2008-11-28 15:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 2:24 timestamps not git-cloned jidanni
2008-11-28 3:08 ` dhruva
2008-11-28 5:06 ` jidanni
2008-11-28 6:59 ` Daniel Barkalow
2008-11-29 8:54 ` Chris Frey
2008-11-29 9:22 ` Stephen R. van den Berg
2008-11-29 10:16 ` Thomas Rast
2008-11-30 0:48 ` jidanni
2008-12-01 9:09 ` Andreas Ericsson
2008-12-01 11:44 ` Jakub Narebski
2008-11-30 1:14 ` Sitaram Chamarty
2008-11-28 5:57 ` David Brown
2008-11-28 14:59 ` Peter Krefting [this message]
2008-11-28 11:51 ` Johannes Schindelin
2008-11-28 12:58 ` Robin Rosenberg
2008-11-28 13:20 ` Johannes Schindelin
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=Pine.LNX.4.64.0811281554560.14606@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--cc=dhruvakm@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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).