News for hackers. Stuff that matters.
Re:How Microsoft Office Moved from Source Depot to Git by mrheosuper on Wednesday June 11, 2025 @09:32PM (#44253541)
- git add .

- git commit -m "First commit"

- git push origin master

- Done

Edit: Do HN people know how to tell whether it's a joke ?

Re:How Microsoft Office Moved from Source Depot to Git by senkora on Wednesday June 11, 2025 @09:57PM (#44253637)
> Microsoft had to collaborate with GitHub to invent the Virtual File System for Git (VFS for Git) just to make this migration possible. Without VFS, a fresh clone of the Office repository (a shallow git clone would take 200 GB of disk space) would take days and consume hundreds of gigabytes.
Re:How Microsoft Office Moved from Source Depot to Git by golergka on Wednesday June 11, 2025 @11:17PM (#44253996)
It takes less than an hour on my third world apartment wifi to download Call of Duty Modern Warfare remake which is over 200 gygabytes. Since we're not talking about remote work here, I think Microsoft offices and servers (probably on local network) might have managed similar bandwidth back then.
Re:How Microsoft Office Moved from Source Depot to Git by TowerTall on Wednesday June 11, 2025 @11:27PM (#44254047)
There is a lot more to it than that. Check out "The largest Git repo on the planet" by Brian Harry who was in charge of the git migration and Azure DevOps (Microsoft's pendant to GitHub)

https://devblogs.microsoft.com/bharry/the-largest-git-repo-o...

Re:How Microsoft Office Moved from Source Depot to Git by dshacker on Wednesday June 11, 2025 @11:37PM (#44254093)
> For context, if we tried this with “vanilla Git”, before we started our work, many of the commands would take 30 minutes up to hours and a few would never complete. The fact that most of them are less than 20 seconds is a huge step but it still sucks if you have to wait 10-15 seconds for everything. When we first rolled it out, the results were much better. That’s been one of our key learnings. If you read my post that introduced GVFS, you’ll see I talked about how we did work in Git and GVFS to change many operations from being proportional to the number of files in the repo to instead be proportional to the number of files “read”. It turns out that, over time, engineers crawl across the code base and touch more and more stuff leading to a problem we call “over hydration”. Basically, you end up with a bunch of files that were touched at some point but aren’t really used any longer and certainly never modified. This leads to a gradual degradation in performance. Individuals can “clean up” their enlistment but that’s a hassle and people don’t, so the system gets slower and slower.

Great quote from him here.

Re:How Microsoft Office Moved from Source Depot to Git by speed_spread on Wednesday June 11, 2025 @10:58PM (#44253912)
Having had yesterday the dubious pleasure of using MS Word for the first time in a decade, I can safely affirm that they could have have just piped the whole Office repo to the Windows equivalent of /dev/null and nothing of value would have been lost.
Re:How Microsoft Office Moved from Source Depot to Git by bigbuppo on Wednesday June 11, 2025 @11:24PM (#44254037)
The worst part about Word is that it has been feature complete since Office 97, except they've made the UI worse each and every version since then. I wish I could get excited about a new version of Office or WordPerfect, but neither Microsoft or Corel has figured out how to innovate in the past three decades. And no, slapping """AI""" in there isn't the solution. There are so many possibities but they just sort of do nothing with it now that they make a few billion a month on Microsoft 365 subscriptions.
Re:How Microsoft Office Moved from Source Depot to Git by samtheprogram on Wednesday June 11, 2025 @11:09PM (#44253954)
This isn’t Reddit. It’s a lame drive-by joke. The system is working.
Re:How Microsoft Office Moved from Source Depot to Git by kirb on Wednesday June 11, 2025 @10:29PM (#44253780)
Don’t do this on a repository with 35+ years of history! That’s all valuable information you want to keep.
Re:How Microsoft Office Moved from Source Depot to Git by speed_spread on Wednesday June 11, 2025 @11:09PM (#44253955)
Anything before Office 2003 you can delete. Anything after Office 2003 you can also delete. There, saved you a few terabytes.
Re:How Microsoft Office Moved from Source Depot to Git by sherdil2022 on Wednesday June 11, 2025 @09:41PM (#44253580)
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.
Re:How Microsoft Office Moved from Source Depot to Git by firesteelrain on Wednesday June 11, 2025 @11:37PM (#44254097)
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.

Re:How Microsoft Office Moved from Source Depot to Git by hulitu on Thursday June 12, 2025 @01:30AM (#44254556)
> 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.