684
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Sep 2023
684 points (97.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
53939 readers
291 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
💰 Please help cover server costs.
founded 1 year ago
MODERATORS
I've had teams not bother to keep proper history when moving from subversion to git and I've also had a DevOps team entirely wipe the history of a new project just because cloning took a long time (and refused to attempt shallow cloning).
So the idea that a company just lets their code "rot" to the point of not even having it anymore because it's just some legacy thing from over a decade ago is totally unsurprising to me.
Just to pile on. I've seen devs throw out the entire git history when moving between repos for ongoing projects.