Modified times are reset to 'checkout time', which is a problem when you work with management scripts & configurations as opposed to application development.

Our main workforce is using version control to share & maintain operational scripts as well as customer configurations.

When a coworker checks out a repo, the modified timestamp is reset to the checkout time as oppsoed to the original time & date.

Since our main tools is SourceTree + Windows Explorer in this case, as well as misc text-editors it is very hard for us to maintain a good overview of what changed & when it changed because of the invalid timestamp.

I've seen the topic & discussion (Atlassian forums / stackoverflow) on why this is by design, due to MAKE in Linux & recompiling. I can understand those arguments.

However, our main taskforce for sourcecontrol is not focusing on any compilation nor Linux.

We're at a point where we need to decide whether it's more practical to use a different platform to share, maintain and update scripts & config-files.

Having the same time on all files & folders makes usage of Windows Explorer as a tool to find what scripts to retire or re-scope is hard.

We strongly desire the option to retain the original timestamps on the files.