How Microsoft Office Moved from Source Depot to Git

Re:How Microsoft Office Moved from Source Depot to Git by smithkl42 on Thursday June 12, 2025 @10:42AM (#44258396)

I used VSS for a few years back in the late 90's and early 2000's. It was better than nothing - barely - but it was very slow, very network intensive (think MS Access rather than SQL), it had very poor merge primitives (when you checked out a file, nobody else could change it), and yes, it was exceedingly prone to corruption. A couple times we just had to throw away history and start over.

[ Parent | on HN ]

Re:How Microsoft Office Moved from Source Depot to Git by electroly on Thursday June 12, 2025 @10:48AM (#44258461)

SourceSafe had a great visual merge tool. You could enable multiple checkouts. VSS had tons of real issues but not enabling multiple checkouts was a pain that companies inflicted on themselves. I still miss SourceSafe's merge tool sometimes.

[ Parent | on HN ]

Re:How Microsoft Office Moved from Source Depot to Git by anonymars on Thursday June 12, 2025 @07:29PM (#44264299)

Have you used Visual Studio's git integration? (Note that you could just kick off the merge elsewhere and use VS to manage the conflicts, then commit from back outside. Etc.)

[ Parent | on HN ]