4 ms·
Highly disagree. As long as the code lives, the commit lives.
by nevon 10y ago
Highly disagree. As long as the code lives, the commit lives.
- jbattle 10y agountil 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
- k__ 10y agoWhat is "The Git Killer"?
- telotortium 10y agoThat'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 https://pijul.org), although Pijul specifically won't become popular because it's licensed under AGPL3.
- jbattle 10y agoyep 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.
- k__ 10y agoI 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.
- Macha 10y agoWe have CVS, SVN, a legacy internal tool for managing git repos and most recently, Bitbucket. And some of these repos go back years. So companies do migrate version control systems.