Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • I understand your answer, but as Git only modifies the files that are modified on remote, does setting the time after the modification really slow down the process so noticeably to disable such feature? Commented Jun 7, 2017 at 23:05
  • Honestly, I'm not completely sure. I'm sure the devs had some reason they came up with when they did it. Commented Jun 7, 2017 at 23:07
  • @DRSDavidSoft -- "touch" is very fast. But writing the code to call touch is a potentially-complicated, potentially-buggy extra feature. When a system (like the earliest versions of Git) is being prototyped, it is important to minimize the number of potentially-buggy features before getting real-world feedback. And once you start getting real-world feedback, you have effectively created standard interface semantics. It think it would be impossible to change this interface's semantics in a backward-compatible way. Commented Jun 17, 2017 at 18:08