That said, it still can be done, although it is not natively supported, you
may do it with some custom tool. By finding the last commit a specific file
was modified in, you may apply the date of the commit to that file.
However, if you have a large repository, looking at this information for
each single file may take really long. Still, it looks like an interesting
project if your build environment really requires it…

On 30 September 2014 21:25, Tom Green <tomgreen1...@gmail.com> wrote:

> Thanks, Konstantin.  That's what I was afraid of.  -- Tom
>
>
>
> On Tuesday, September 30, 2014 11:17:11 AM UTC-4, Tom Green wrote:
>
>> I am working in Windows with GIT.
>>
>> When I need to fix an older released version of our system I CHECKOUT
>> that version. GIT restores the files in my working directory to the
>> *contents* they had on that time. But it does not restore the *file
>> dates*.
>>
>> This causes me problems because many of the tools we use look at file
>> dates, for example our debugger. I could make a copy on disk (or a zip
>> file) of each branch before I switch away from it, instead of using GIT for
>> this, but that really defeats the purpose of GIT.
>>
>> Is there a configuration option or other means to change that GIT
>> behavior?
>>
>> TIA.
>>
>  --
> 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.
>

-- 
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