<?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 for Version Control Blog</title>
	<atom:link href="http://www.versioncontrolblog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.versioncontrolblog.com</link>
	<description>Version control, software configuration management (SCM)</description>
	<lastBuildDate>Thu, 29 Oct 2009 13:18:01 +0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Upgrading Drupal with Git by bhirsch</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1943</link>
		<dc:creator>bhirsch</dc:creator>
		<pubDate>Thu, 29 Oct 2009 13:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1943</guid>
		<description>I just started using git for version control with Drupal. I love it, but there&#039;s one thing that&#039;s driving me crazy: For some reason git merges my changes to settings.php every time I checkout a branch.

I want settings.php in my master branch to connect to one mysql database, while settings.php in the second branch should connect to another. But every time I switch branches, I get this error: 

bhirsch$ git checkout master
error: unable to unlink old &#039;sites/default/settings.php&#039; (Permission denied)
M	sites/default/settings.php
Switched to branch &#039;master&#039;
bhirsch$ 

Here are suggestions I&#039;ve picked up elsewhere that I&#039;ve tried, but haven&#039;t worked:
chmod og+w .git/object/16 
and 
chmod g+ws .git/

Any suggestions you can offer would be greatly appreciated.</description>
		<content:encoded><![CDATA[<p>I just started using git for version control with Drupal. I love it, but there&#8217;s one thing that&#8217;s driving me crazy: For some reason git merges my changes to settings.php every time I checkout a branch.</p>
<p>I want settings.php in my master branch to connect to one mysql database, while settings.php in the second branch should connect to another. But every time I switch branches, I get this error: </p>
<p>bhirsch$ git checkout master<br />
error: unable to unlink old &#8217;sites/default/settings.php&#8217; (Permission denied)<br />
M	sites/default/settings.php<br />
Switched to branch &#8216;master&#8217;<br />
bhirsch$ </p>
<p>Here are suggestions I&#8217;ve picked up elsewhere that I&#8217;ve tried, but haven&#8217;t worked:<br />
chmod og+w .git/object/16<br />
and<br />
chmod g+ws .git/</p>
<p>Any suggestions you can offer would be greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by In the town called Workflow, lived three friends - Git, CVS and Drupal&#8230;. &#124; ArvinderKang.com</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1942</link>
		<dc:creator>In the town called Workflow, lived three friends - Git, CVS and Drupal&#8230;. &#124; ArvinderKang.com</dc:creator>
		<pubDate>Tue, 03 Mar 2009 02:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1942</guid>
		<description>[...] by Version Control Blog, ToolmanTim and [...]</description>
		<content:encoded><![CDATA[<p>[...] by Version Control Blog, ToolmanTim and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by squadette</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1937</link>
		<dc:creator>squadette</dc:creator>
		<pubDate>Tue, 09 Dec 2008 23:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1937</guid>
		<description>inc,

I do not :)</description>
		<content:encoded><![CDATA[<p>inc,</p>
<p>I do not :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by inc</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1936</link>
		<dc:creator>inc</dc:creator>
		<pubDate>Mon, 08 Dec 2008 07:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1936</guid>
		<description>Thank you for the excellent article, but one thing is undefined.
How do you include changes made in Drupal database in your repositaries?</description>
		<content:encoded><![CDATA[<p>Thank you for the excellent article, but one thing is undefined.<br />
How do you include changes made in Drupal database in your repositaries?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by Drupal Development and Deployment using Git &#124; ruzee.com - Steffen Rusitschka</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1770</link>
		<dc:creator>Drupal Development and Deployment using Git &#124; ruzee.com - Steffen Rusitschka</dc:creator>
		<pubDate>Sat, 25 Oct 2008 15:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1770</guid>
		<description>[...] This part is similar to the method shown by the Version Control Blog, except I will not use cloning but branching instead. [...]</description>
		<content:encoded><![CDATA[<p>[...] This part is similar to the method shown by the Version Control Blog, except I will not use cloning but branching instead. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dave Dribin: &#8220;Choosing a Distributed Version Control System&#8221; by dave.k.smith</title>
		<link>http://www.versioncontrolblog.com/2008/02/10/dave-dribin-choosing-a-distributed-version-control-system/comment-page-1/#comment-1287</link>
		<dc:creator>dave.k.smith</dc:creator>
		<pubDate>Sat, 12 Jul 2008 00:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2008/02/10/dave-dribin-choosing-a-distributed-version-control-system/#comment-1287</guid>
		<description>Another comment related to the Version Control Blog itself:  I am unable to modify my own profile on this site.  When I click on my username above this comment box for example, I get the following:

Forbidden

You don&#039;t have permission to access /wp-admin/profile.php on this server.
Apache/2.2.8 (Fedora) Server at versioncontrolblog.com Port 80</description>
		<content:encoded><![CDATA[<p>Another comment related to the Version Control Blog itself:  I am unable to modify my own profile on this site.  When I click on my username above this comment box for example, I get the following:</p>
<p>Forbidden</p>
<p>You don&#8217;t have permission to access /wp-admin/profile.php on this server.<br />
Apache/2.2.8 (Fedora) Server at versioncontrolblog.com Port 80</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dave Dribin: &#8220;Choosing a Distributed Version Control System&#8221; by dave.k.smith</title>
		<link>http://www.versioncontrolblog.com/2008/02/10/dave-dribin-choosing-a-distributed-version-control-system/comment-page-1/#comment-1286</link>
		<dc:creator>dave.k.smith</dc:creator>
		<pubDate>Sat, 12 Jul 2008 00:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2008/02/10/dave-dribin-choosing-a-distributed-version-control-system/#comment-1286</guid>
		<description>The URLs on this page &quot;Choosing a Distributed Version Control System&quot; and &quot;Why I Chose Mercurial&quot; look right on initial load of the page (when I hover my mouse over these links), but when I click the links, the URL gets garbled (perhaps with a server-side rewrite or something) to the following (using the second link as an example):

http://versioncontrolblog.com/r/http://www.dribin.org/dave/blog/archives/2007/12/30/why_mercurial/</description>
		<content:encoded><![CDATA[<p>The URLs on this page &#8220;Choosing a Distributed Version Control System&#8221; and &#8220;Why I Chose Mercurial&#8221; look right on initial load of the page (when I hover my mouse over these links), but when I click the links, the URL gets garbled (perhaps with a server-side rewrite or something) to the following (using the second link as an example):</p>
<p><a href="http://versioncontrolblog.com/r/http://www.dribin.org/dave/blog/archives/2007/12/30/why_mercurial/"  rel="nofollow">http://versioncontrolblog.com/r/http://www.dribin.org/dave/blog/archives/2007/12/30/why_mercurial/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by drew</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-1266</link>
		<dc:creator>drew</dc:creator>
		<pubDate>Thu, 26 Jun 2008 00:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-1266</guid>
		<description>This is very useful, thanks. 
There is a mirror of the entire Drupal cvs tree here, http://mikkel.hoegh.org/blog/2008/a_git_mirror_for_drupal_cvs 

This means you can use the Drupal Git repository (sounds like a fun place) as the pristine version and clone or branch it into other sites. I&#039;m not to sure if having the entire Drupal tree is a good idea though, since Git will pass the whole history from clone to clone. It makes it ridiculously easy to switch drupal versions for testing.

The best thing about this method is that it doesn&#039;t break the update status module like working with a cvs checkout does.</description>
		<content:encoded><![CDATA[<p>This is very useful, thanks.<br />
There is a mirror of the entire Drupal cvs tree here, <a href="http://mikkel.hoegh.org/blog/2008/a_git_mirror_for_drupal_cvs" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://mikkel.hoegh.org/blog/2008/a_git_mirror_for_drupal_cvs');" rel="nofollow">http://mikkel.hoegh.org/blog/2008/a_git_mirror_for_drupal_cvs</a> </p>
<p>This means you can use the Drupal Git repository (sounds like a fun place) as the pristine version and clone or branch it into other sites. I&#8217;m not to sure if having the entire Drupal tree is a good idea though, since Git will pass the whole history from clone to clone. It makes it ridiculously easy to switch drupal versions for testing.</p>
<p>The best thing about this method is that it doesn&#8217;t break the update status module like working with a cvs checkout does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Microsoft Codeplex by John Collis</title>
		<link>http://www.versioncontrolblog.com/2006/10/08/codeplex/comment-page-1/#comment-815</link>
		<dc:creator>John Collis</dc:creator>
		<pubDate>Thu, 06 Mar 2008 12:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2006/10/08/codeplex/#comment-815</guid>
		<description>Folks:

North America&#039;s Premiere hosted VSTS/TFS service is now live!

Check us out at:
www.teamdevcentral.com

Cheers,

John Collis</description>
		<content:encoded><![CDATA[<p>Folks:</p>
<p>North America&#8217;s Premiere hosted VSTS/TFS service is now live!</p>
<p>Check us out at:<br />
<a href="http://www.teamdevcentral.com" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://www.teamdevcentral.com');" rel="nofollow">http://www.teamdevcentral.com</a></p>
<p>Cheers,</p>
<p>John Collis</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Drupal with Git by squadette</title>
		<link>http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/comment-page-1/#comment-797</link>
		<dc:creator>squadette</dc:creator>
		<pubDate>Fri, 22 Feb 2008 20:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://versioncontrolblog.com/2007/08/02/upgrading-drupal-with-git/#comment-797</guid>
		<description>benjamin,

fixed!  stupid wordpress.</description>
		<content:encoded><![CDATA[<p>benjamin,</p>
<p>fixed!  stupid wordpress.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
