5 ms·
But why put that info in commit message instead of a comment in the file itself?
by mamon 6y ago
But why put that info in commit message instead of a comment in the file itself?
- colordrops 6y agoOr even in the compile error message itself.
- chris_wot 6y agoBecause comments can be tedious and get out of sync with the repo. Why not check the git history? I wish more repos could be like this!
- adrianmonk 6y ago> Why not check the git history? Because that is effort every person who uses the file has to do over and over again, whereas maintaining the file is effort that has to be done once by one person.
- chris_wot 6y agoIt sounds like you want a manual. Personal preference I guess. The maintainers seem to have decided to keep it in the history. It's not like this was ever meant for anything other than git itself.
- astrobe_ 6y agoIf all you have is Git everything looks like a commit.
- aendruk 6y agoI really wish tooling like this was more common: https://github.com/eamodio/vscode-gitlens/tree/v11.2.1#current-line-blame- https://github.com/eamodio/vscode-gitlens/tree/v11.2.1#curre... (screenshot) > Current Line Blame: Adds an unobtrusive, customizable, and themable, blame annotation at the end of the current line
- skeletal88 6y agoSomeone here commented to use git blame to find the commit that banned the functions and read the commits. These people making the suggestions.. must hate other people and their time. Also, what if someone.. for example runs a code formatter on the file, making git blame useless? Is it really so difficult to make a manual or explain properly in the comments about what replacements to use?