Not doubting it but I don't understand how a shallow clone of OneNote would be 200GB.
Shallow clone of all of office, not onenote.
Oh alright. Thanks.
Microsoft Office migration from Source Depot to Git
81–90 of 290 posts
Re: Microsoft Office migration from Source Depot to Git
#82This article makes out thousands of engineers that are good enough to qualify at Microsoft and work on Office but haven't used git yet? That sounds a bit overplayed tbh, if you haven't used git you must live under a rock. You can't use Source Depot at home. Overall good story though
It's entirely plausible that a long-term engineer at Microsoft wouldn't have have used git. I'm sure a considerable number of software engineers don't program as a hobby.
Re: Microsoft Office migration from Source Depot to Git
#83This article makes out thousands of engineers that are good enough to qualify at Microsoft and work on Office but haven't used git yet? That sounds a bit overplayed tbh, if you haven't used git you must live under a rock. You can't use Source Depot at home. Overall good story though
You’d be surprised at the amount of people at Microsoft that their entire career have been at Microsoft (pre-git-creation) that never used Git. Git is relatively new (2005) but source control systems are not.
That's still two decades. Git is so popular Microsoft bought one of the major forges 7 years ago.
To have never touched it in the last decade? You've got a gap in your CV.
Re: Microsoft Office migration from Source Depot to Git
#84I was on the team that migrated Microsoft from XNS to TCP/IP - it was way less involved, but similar lessons learned. Migrating from MSMAIL -> Exchange, though - that was rough
Is that what inspired the "Exchange: The Most Feared and Loathed Team in Microsoft" license plate frames? I'm probably getting a bit of the wording wrong. It's been nearly 20 years since I saw one.
Re: Microsoft Office migration from Source Depot to Git
#85I was on the team that migrated Microsoft from XNS to TCP/IP - it was way less involved, but similar lessons learned. Migrating from MSMAIL -> Exchange, though - that was rough
Is that what inspired the "Exchange: The Most Feared and Loathed Team in Microsoft" license plate frames? I'm probably getting a bit of the wording wrong. It's been nearly 20 years since I saw one.
Probably. A lot of people really loved MSMAIL; not so much Exchange.
I have more long, boring stories about projects there, but that’s for another day
Re: Microsoft Office migration from Source Depot to Git
#86Earlier quoted context omitted.
What would ZFS do for those issues? I guess maybe deduplication, but otherwise I'm not thinking of anything that you can't do with mount --bind and overlays (and I'm not even sure ZFS would replace overlays)
Snapshots seems to be a cheap feature in ZFS but are expensive everywhere else, for example. OverlayFS has had performance issues on Linux for a while (once you start composing a bunch of overlays, the performance drops dramatically as well as you start hitting limits on number of overlays).
Nowadays the ZFS advantage for snapshots is no longer true.
Other file systems, e.g. the much faster XFS, have equally efficient snapshots.
Re: Microsoft Office migration from Source Depot to Git
#87Earlier quoted context omitted.
You’d be surprised at the amount of people at Microsoft that their entire career have been at Microsoft (pre-git-creation) that never used Git. Git is relatively new (2005) but source control systems are not.
That's still two decades. Git is so popular Microsoft bought one of the major forges 7 years ago. To have never touched it in the last decade? You've got a gap in your CV.
Not everyone wants to code for hobby, so if their work not uses git then they too will not use it.
Re: Microsoft Office migration from Source Depot to Git
#88Earlier quoted context omitted.
You’d be surprised at the amount of people at Microsoft that their entire career have been at Microsoft (pre-git-creation) that never used Git. Git is relatively new (2005) but source control systems are not.
That's still two decades. Git is so popular Microsoft bought one of the major forges 7 years ago. To have never touched it in the last decade? You've got a gap in your CV.
[deleted]
Re: Microsoft Office migration from Source Depot to Git
#89This article makes out thousands of engineers that are good enough to qualify at Microsoft and work on Office but haven't used git yet? That sounds a bit overplayed tbh, if you haven't used git you must live under a rock. You can't use Source Depot at home. Overall good story though
Sure you can use Source Depot (actually Perforce) at home: https://www.perforce.com/p/vcs/vc/free-version-control