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,
freefile
Hi Vincent,
Sorry, but that is one thing that Git, bu design, does not do.
Philip
- Original Message -
From: Croqueur Fou
To: Git for human beings
Sent: Thursday, September 29, 2016 2:32 PM
Subject: [git-users] File timestamp changed after reverting back to an
original commit
On Thu, 29 Sep 2016 06:32:32 -0700 (PDT)
Croqueur Fou 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 beh
Links are an awkward beast, along with path mangling (as you mention)...
Do have a look at the FAQs https://git-for-windows.github.io/ (link [1] at the
top right), and the release notes (in the programme files Git directory)
There are a few issue reports such as
https://github.com/git-for-wind
But make sure that the ONLY difference between the tagged version with the
functionality and the next commit is the removal. Don't pretty the code,
don't correct one typo, don't do ANYTHING but remove files.
If, you have to do anything in addition to removing files, I would do that
stuff in the fi
