Re: timestamps not git-cloned

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Peter Krefting
Date: Friday, November 28, 2008 - 7:59 am

Hi!

dhruva:


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/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
timestamps not git-cloned, jidanni, (Thu Nov 27, 7:24 pm)
Re: timestamps not git-cloned, dhruva, (Thu Nov 27, 8:08 pm)
Re: timestamps not git-cloned, David Brown, (Thu Nov 27, 10:57 pm)
Re: timestamps not git-cloned, Johannes Schindelin, (Fri Nov 28, 4:51 am)
Re: timestamps not git-cloned, Robin Rosenberg, (Fri Nov 28, 5:58 am)
Re: timestamps not git-cloned, Johannes Schindelin, (Fri Nov 28, 6:20 am)
Re: timestamps not git-cloned, Peter Krefting, (Fri Nov 28, 7:59 am)