4 ms·
> I write my comments in commit messages because those are valid forever. Only until someone moves a file to a new directory. Now this file shows up as a new f
by nine_zeros 5y ago
> I write my comments in commit messages because those are valid forever.
Only until someone moves a file to a new directory. Now this file shows up as a new file with no history.
Also, you hope to never change your version control system because that change will erase the history.
Relying on commit messages is sometimes just not good enough.
- cerved 5y agoNo it doesn't. At least git tracks and follow renames
- masklinn 5y ago> Only until someone moves a file to a new directory. Now this file shows up as a new file with no history. Git will usually be able to link the two back, unless the move was combined with a lot of changes, as it does not record moves but infers them. Even if it can't link them, the "creation" commit will visibly remove the old file, at which point you can... log / blame on the previous location and keep going. > Also, you hope to never change your version control system because that change will erase the history. Of course not, there are conversion tools between basically all VCS, and anyone tasked with such a migration who is not a complete goober will use them in order to maintain the historical record. At $dayjob we've got history spanning over 3 different VCS and more than 15 years, and that's including weird stuff like splitting and merging repositories.