Comment by sherdil2022
3 days ago
If it were that simple, would 100s of engineers spend so much time and effort? They did what they have to and spent the time and energy to maintain some semblance of commit and change history.
3 days ago
If it were that simple, would 100s of engineers spend so much time and effort? They did what they have to and spent the time and energy to maintain some semblance of commit and change history.
GP has a valid point. We had a Git repo managed in BitBucket that was gigantic because it contained binary files and the team didn’t know about LFS and storing them in an external tool like Artifactory. So checkouts took forever and even with shallow clones it took forever. With a CI/CD system running constantly and tests needing constant full coverage and hundreds of developers well it eats into developers time. We can’t just prune all the branches well because of compliance rules.
So we ended up removing all the binary artifacts before cloning into a new repo then making the old repo as read only.
Microsoft seemed to want to mirror everything rather than keep source depot alive.
We had another case where we had a subversion system that went out of security compliance that we simply ported to our git systems and abandoned it.
So my guess is they wanted everything to look the same and not just importing the code.
> If it were that simple, would 100s of engineers spend so much time and effort?
Taking into acvount that they rounded corners in Office, I would say, yes.