> From: Thomas Ferris Nicolaisen <tfn...@gmail.com> > > > Hello -- I just did a clone of a (bare) repo and notices that all files > > have the same date/time, that is the time of the clone -- is this the way > > this is suppose to work? > > Yes, this is normal. Git doesn't store much meta-information about files. > Strictly speaking, Git tracks contents of files, not the files themselves.
Actually, this is *intended*, and most SCMs do this. The reason is that people use "make" to regenerate derived files, and since *this* copy of the foo.c file has just been created, any previously existing copy of foo.o must be assumed to be out-of-date, and that is indicated by the creation date of foo.c. Of course, during a clone operation, this argument doesn't apply, because no derived files will exist, but any later operation on the repository that changes the controlled foo.c file must give foo.c the *current* date, not the date that those particular contents were added to the repository. Dale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
