On Thu, 29 Sep 2016 06:32:32 -0700 (PDT)
Croqueur Fou <vincent.le.croqu...@gmail.com> wrote:

> When checking-out back to an original branch or commit, the
> time-stamps of the changed files is reset to the current timedate,
> not to their original time-stamps. Is there an option in git to
> change this behavior ? The actual behavior causes old fashioned
> time-stamp based VCS (winmerge, freefilesync, ...) to see the files
> reverted back as "changed" while they are not. 
> Any thoughts ?

IMO this is implemented explicitly to support make-like tools which use
timestamps to determine whether they have to regenerate the dependent
file (such as recompile source files to produce object files).

The idea is that when you check some version out and build it and then check 
some other version out and build it, it has to build correctly, and in order to 
do that, the timestamps on the source files had to be updated.

You can just google for git+checkout+timestamps to look for workarounds.

You can find one of them linked to in the second answer at [1].


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/d/optout.

Reply via email to