<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>An Introduction to Git – Kevin Webber</title><link>https://kevinwebber.ca/series/migrating-to-git/</link><description>Latest chapters in An Introduction to Git</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 05 May 2026 18:15:25 +0000</lastBuildDate><atom:link href="https://kevinwebber.ca/series/migrating-to-git/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Safely Migrate to Git</title><link>https://kevinwebber.ca/series/migrating-to-git/03-safely-migrating-from-svn-to-git/</link><pubDate>Sun, 09 Sep 2012 00:00:00 +0000</pubDate><guid isPermaLink="true">https://kevinwebber.ca/series/migrating-to-git/03-safely-migrating-from-svn-to-git/</guid><description>This is the third and final part in a three part series about migrating to Git. I recommend reading part one and part two if you haven’t already. Migrating to Git is worth it, but it’s not a trivial decision. If you’re ready to proceed with a migration to Git, congratulations! You’re about to start using one of the best development tools available today. Pre-migration steps Anyone who has worked with me knows I’m a big fan of checklists, and the transition to Git is non-trivial enough to warrant a solid understanding of the questions that should be answered before pulling the trigger on migration.</description></item><item><title>What to Consider Before Migrating to Git</title><link>https://kevinwebber.ca/series/migrating-to-git/02-what-to-consider/</link><pubDate>Sun, 09 Sep 2012 00:00:00 +0000</pubDate><guid isPermaLink="true">https://kevinwebber.ca/series/migrating-to-git/02-what-to-consider/</guid><description>This is the second part of a three part series about migrating to Git. If you haven’t read part one and are unfamiliar with the advantages of Git, you should check it out. Migrating to Git, Part 1: Advantages If you already understand the benefits of Git, or have already read part one, welcome to part two in the series! We’re going to discuss certain pre-conditions of a migration to Git and make sure your team is ready for the transition.</description></item><item><title>Advantages of Git Over Legacy Version Control Systems</title><link>https://kevinwebber.ca/series/migrating-to-git/01-advantages-of-git/</link><pubDate>Sun, 09 Sep 2012 00:00:00 +0000</pubDate><guid isPermaLink="true">https://kevinwebber.ca/series/migrating-to-git/01-advantages-of-git/</guid><description>Git is unlike typical version control systems. Sure, Git is used to version files, but how is that any different than SVN or SourceSafe or ClearCase? Git expects developers to understand how it works under the hood. It expects developers to be comfortable with the command line to get the most out of it. It provides very little in the way of convention and expects you to design your own workflow simply by using it as another tool in your arsenal. Git is not an out-of-the box solution. If you plan to transition to Git you also need to set aside time to examine your overall development process. You won’t get the most out of it otherwise and will possibly experience a challenging migration.</description></item></channel></rss>