Re:What a good commit message looks like (2011)
by nevon on Thursday January 26, 2017 @11:19AM
(#13492606)
Highly disagree. As long as the code lives, the commit lives.
[ Parent
| on HN ]
Re:What a good commit message looks like (2011)
by jbattle on Thursday January 26, 2017 @11:23AM
(#13492657)
until the git killer comes along and the team decides how much history they are willing to migrate. I've seen it happen every 5(?) years across several companies. Ironically it's always the oldest commit messages that turn out to be the most valuable because newer changes people remember
Re:What a good commit message looks like (2011)
by k__ on Thursday January 26, 2017 @11:28AM
(#13492693)
What is "The Git Killer"?
Re:What a good commit message looks like (2011)
by telotortium on Thursday January 26, 2017 @11:47AM
(#13492878)
That's just a generic stand-in for any new version control system that becomes popular enough to display Git. For example, Pijul (https://pijul.org), although Pijul specifically won't become popular because it's licensed under AGPL3.
Re:What a good commit message looks like (2011)
by jbattle on Thursday January 26, 2017 @12:30PM
(#13493299)
yep as telo.. said - whatever will inevitably supercede git. In my own work it was VSS > Perforce > svn > git
All of those were good choices when they were new, and suboptimal choices when the next better solution came along.
Re:What a good commit message looks like (2011)
by k__ on Thursday January 26, 2017 @12:37PM
(#13493356)
I had the feeling companies would just stick to their thing.
Last I worked with used CVS and always talked about switching to SVN, but never did.