3 ms·

Most of the details are out there but … > in that he had apparently downloaded a copy of everything … is a day in the office? I've done this, particularly at

Most of the details are out there but … > in that he had apparently downloaded a copy of everything … is a day in the office? I've done this, particularly at places that are "one repo == one project" organized (i.e., not monorepo): e.g., if I make a breaking change to a library, I'm going to update all the uses of that. Still to this day, the easiest way to do that is locally, with command line tooling.

jonhohle 3y ago
Places with reasonable build systems can do that for you. For example, poudriere on FreeBSD.
indrora 3y ago
If you look at the Nintendo Gigaleaks, you'll discover that most of Nintendo hardware had one single CVS (later SVN) repository that held everything. Same with BroadOn, even up into 2010, when the cvs backup was taken. It's fairly well known that Google maintained a Stinky monorepo for a long time and one of the risks is someone just going and slurping the whole thing up onto a big enough drive and walking out the door.