Re: preserving mtime

On Sun, Nov 18, 2007 at 09:45:11 +0100, Mike Hommey wrote:

On Sat, Nov 17, 2007 at 10:22:36AM -0800, Wayne Davison wrote:

quoted

On Fri, Nov 16, 2007 at 11:15:34AM +0100, Andreas Ericsson wrote:

quoted

quoted

is it possible to tell git to preserve the file modification time in
a checked out copy?

quoted

Fabrizio Pollastri wrote:
No. Doing so would seriously break build-systems.

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
being set to the clone date.  Then, files that are being updated would
get their time set as they do now.  I supposed I'll just use the handy
git-set-file-times script (mentioned in another reply) every time I do
a clone.

For completeness, it would make sense to do so every time you git
checkout (like, when switching branches).

 - That would still screw-up make hard. You know, checking out does NOT
   delete any untracked files.

 - There is no such thing as last modification time in git. Because there is
   no file history in git. (Besides, what would be last modification time of
   a file that was last modified in two parents, for example?)

-- 
						 Jan 'Bulb' Hudec [off-list ref]