3 ms·
I’m realizing this might not cross some developers minds because the current time in that context is attached to the commit when it was added or changed. I do
by steve_adams_86 2y ago
I’m realizing this might not cross some developers minds because the current time in that context is attached to the commit when it was added or changed.
I do this quite often. I probably shouldn’t, though. It’s only useful if you’re looking at commit logs or have an inline ‘last changed by [author] on [date]’ helper in your IDE.
Then again, even that could be made wrong by future edits.
- Groxx 2y agoYeah, there are frequently ways to figure out what date a relative measure is referring to; it's one of the best things about version control being a true norm in this field. But it's a few extra steps (depending on the UI), and many will not take those steps. They'll just trust it (far beyond when it's relevant), or think "that's probably old" and doubt it (immediately, because old docs are so common). It's relatively minor, but it's extremely easy to prevent, and just a better habit when communicating with the future.
- codeflo 2y agoAnd that’s assuming the repository never gets reorganized in any way that doesn’t perfectly preserve history — which over long timespans, is bound to happen at some point.