<?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: Bzr keeps easing my pain</title>
	<atom:link href="http://inodes.org/2009/04/03/bzr-keeps-easing-my-pain/feed/" rel="self" type="application/rss+xml" />
	<link>http://inodes.org/2009/04/03/bzr-keeps-easing-my-pain/</link>
	<description>Moo - Development, Trouble-shooting and Random thoughts...</description>
	<lastBuildDate>Thu, 01 Mar 2012 22:58:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: johnf</title>
		<link>http://inodes.org/2009/04/03/bzr-keeps-easing-my-pain/comment-page-1/#comment-2498</link>
		<dc:creator>johnf</dc:creator>
		<pubDate>Sat, 04 Apr 2009 01:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://inodes.org/blog/?p=127#comment-2498</guid>
		<description>@Erik

I haven&#039;t looked into it that much as it&#039;s not my use case. But I&#039;m pretty sure you could have a git repo on your web server branch from it. Then branch from upstream make your changes, merge them into your servers branch and push.

Also bzr has a git-serve command which looks like it will sit on the server and publish your bzr branch as a git branch. Ie people can connect to &quot;bzr git-serve&quot; with a git client. Which is probably the method I&#039;d go for. Since I natively get to use bzr but people can pull from me using git.</description>
		<content:encoded><![CDATA[<p>@Erik</p>
<p>I haven&#8217;t looked into it that much as it&#8217;s not my use case. But I&#8217;m pretty sure you could have a git repo on your web server branch from it. Then branch from upstream make your changes, merge them into your servers branch and push.</p>
<p>Also bzr has a git-serve command which looks like it will sit on the server and publish your bzr branch as a git branch. Ie people can connect to &#8220;bzr git-serve&#8221; with a git client. Which is probably the method I&#8217;d go for. Since I natively get to use bzr but people can pull from me using git.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://inodes.org/2009/04/03/bzr-keeps-easing-my-pain/comment-page-1/#comment-2497</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Fri, 03 Apr 2009 23:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://inodes.org/blog/?p=127#comment-2497</guid>
		<description>Pulling from git using bzr is all very fine, but once you make local changes, how do you push them back to  upstream? If you were using git,  you&#039;d put a copy of your branch on a web server and get upstream  to pull from that. Obviously, that&#039;s not going to work on if you pull with bzr.</description>
		<content:encoded><![CDATA[<p>Pulling from git using bzr is all very fine, but once you make local changes, how do you push them back to  upstream? If you were using git,  you&#8217;d put a copy of your branch on a web server and get upstream  to pull from that. Obviously, that&#8217;s not going to work on if you pull with bzr.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

