What's the connection (if any) between "Source Depot" and TFSVC?
Microsoft Office migration from Source Depot to Git
71–80 of 290 posts
Re: Microsoft Office migration from Source Depot to Git
#72I spent nearly a week of my Microsoft internship in 2016 adding support for Source Depot to the automated code reviewer that I was building ( https://austinhenley.com/blog/featurestheywanted.html ) despite having no idea what Source Depot was! Quite a few devs were still using it even then. I wonder if everything has been migrated to git yet.
Re: Microsoft Office migration from Source Depot to Git
#73> Authenticity mattered more than production value. Thanks for sharing this authentic story! As an ex-MSFT in a relatively small product line that only started switching to Git from SourceDepot in 2015, right before I left, I can truly empathize with how incredible a job you guys have done!
Yeah, it was a whole journey. I can't believe it happened. Thanks for your comment.
Re: Microsoft Office migration from Source Depot to Git
#74Re: Microsoft Office migration from Source Depot to Git
#75Overall good story though
Re: Microsoft Office migration from Source Depot to Git
#76Earlier quoted context omitted.
I didn't even know Microsoft SourceSafe existed.
Lucky you. Definitely one of the worst tools I’ve had the displeasure of working with. Made worse by people building on top of it for some insane reason.
Re: Microsoft Office migration from Source Depot to Git
#77Not doubting it but I don't understand how a shallow clone of OneNote would be 200GB.
Re: Microsoft Office migration from Source Depot to Git
#78We communicated the same information through multiple channels: weekly emails, Teams, wiki docs, team presentations, and office hours. The rule: if something was important, people heard it at least 3 times through different mediums. If only this were standard. Last week I received the only notification that a bunch of internal systems were being deleted in two weeks . No scream test, no archiving, just straight delet…
Even with this, there were many surprised people. I'm still amazed at all of the people that can ignore everything and just open their IDE and code (and maybe never see teams or email)
Re: Microsoft Office migration from Source Depot to Git
#79This 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
Re: Microsoft Office migration from Source Depot to Git
#80Not doubting it but I don't understand how a shallow clone of OneNote would be 200GB.