<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Git on Mark Gottscho, Ph.D.</title>
		<link>https://markgottscho.com/tags/git/</link>
		<description>Recent content in Git on Mark Gottscho, Ph.D.</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Jan 2015 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://markgottscho.com/tags/git/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A Brief Git Tutorial for Collaborative Research</title>
				<link>https://markgottscho.com/posts/2015/01/24/a-brief-git-tutorial-for-collaborative-research/</link>
				<pubDate>Sat, 24 Jan 2015 00:00:00 +0000</pubDate>
				<guid>https://markgottscho.com/posts/2015/01/24/a-brief-git-tutorial-for-collaborative-research/</guid>
				<description>&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;Continuing in the trend I’ve established with some technical tutorials that have proven to be useful to others, I’ve decided to write another brief one, this time focusing on Git version control for researchers.&#xA;Why the emphasis on researchers? One often comes across academic code that is poorly documented, or there are various copies of the code being developed simultaneously by different people, none of whom communicate their changes to one another, making collaboration and follow-up work harder.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
	</channel>
</rss>
