<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Manage Local Versions with Git</title>
	<atom:link href="http://www.digizenstudio.com/blog/2008/07/31/manage-local-versions-with-git/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digizenstudio.com/blog/2008/07/31/manage-local-versions-with-git/</link>
	<description>Jing Xue's Weblog</description>
	<lastBuildDate>Thu, 27 Oct 2011 20:25:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jing Xue</title>
		<link>http://www.digizenstudio.com/blog/2008/07/31/manage-local-versions-with-git/comment-page-1/#comment-102637</link>
		<dc:creator>Jing Xue</dc:creator>
		<pubDate>Fri, 08 Aug 2008 01:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.digizenstudio.com/blog/?p=161#comment-102637</guid>
		<description>@Imran,

Yes, templates work. I have used those before - when there wasn&#039;t git. :-) Although they do come up short compared to actually having the local files:

1. An obvious one: the local files aren&#039;t git-managed. So if I want to clone the repo _locally_, I&#039;d have to manually copy them over.

2. When db-config.properties.template changes, the change has to be manually merged to db-config.properties, whereas with git there is a good chance it&#039;ll get automatically merged.

3. Not all the files can made into templates - for instance, Eclipse&#039;s .class and .project files.

@Nadeem,

You are right. Git checkout -b would be more straightforward.</description>
		<content:encoded><![CDATA[<p>@Imran,</p>
<p>Yes, templates work. I have used those before &#8211; when there wasn&#8217;t git. <img src='http://www.digizenstudio.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Although they do come up short compared to actually having the local files:</p>
<p>1. An obvious one: the local files aren&#8217;t git-managed. So if I want to clone the repo _locally_, I&#8217;d have to manually copy them over.</p>
<p>2. When db-config.properties.template changes, the change has to be manually merged to db-config.properties, whereas with git there is a good chance it&#8217;ll get automatically merged.</p>
<p>3. Not all the files can made into templates &#8211; for instance, Eclipse&#8217;s .class and .project files.</p>
<p>@Nadeem,</p>
<p>You are right. Git checkout -b would be more straightforward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nadeem Bitar</title>
		<link>http://www.digizenstudio.com/blog/2008/07/31/manage-local-versions-with-git/comment-page-1/#comment-102176</link>
		<dc:creator>Nadeem Bitar</dc:creator>
		<pubDate>Tue, 05 Aug 2008 19:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.digizenstudio.com/blog/?p=161#comment-102176</guid>
		<description>You can use git checkout -b  to create a branch and switch to it.</description>
		<content:encoded><![CDATA[<p>You can use git checkout -b  to create a branch and switch to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Imran M Yousuf</title>
		<link>http://www.digizenstudio.com/blog/2008/07/31/manage-local-versions-with-git/comment-page-1/#comment-101822</link>
		<dc:creator>Imran M Yousuf</dc:creator>
		<pubDate>Mon, 04 Aug 2008 05:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.digizenstudio.com/blog/?p=161#comment-101822</guid>
		<description>For cases where a file needs to edited in local workspace one can actually check in a template of the file and then users can create their own version of it. I would actually suggest the template way.

For example db-config.properties is a file that would require one to sepcify their subjective connection parameters I would add a db-config.properties.template and have users create their own version of it. Additionally I would also add it to git&#039;s ignore list (.gitignore) so that the file does not show up in index and does not affected due to git reset command.</description>
		<content:encoded><![CDATA[<p>For cases where a file needs to edited in local workspace one can actually check in a template of the file and then users can create their own version of it. I would actually suggest the template way.</p>
<p>For example db-config.properties is a file that would require one to sepcify their subjective connection parameters I would add a db-config.properties.template and have users create their own version of it. Additionally I would also add it to git&#8217;s ignore list (.gitignore) so that the file does not show up in index and does not affected due to git reset command.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

