<?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: Sharing a public Darcs repo over HTTP [flow chart]</title>
	<atom:link href="http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/feed" rel="self" type="application/rss+xml" />
	<link>http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart</link>
	<description>mah-soo-koh-me</description>
	<lastBuildDate>Thu, 04 Mar 2010 22:53:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Stosberg</title>
		<link>http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/comment-page-1#comment-83</link>
		<dc:creator>Mark Stosberg</dc:creator>
		<pubDate>Wed, 19 Mar 2008 02:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart#comment-83</guid>
		<description>Amusing. I love it!

  Mark</description>
		<content:encoded><![CDATA[<p>Amusing. I love it!</p>
<p>  Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: masukomi</title>
		<link>http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/comment-page-1#comment-29</link>
		<dc:creator>masukomi</dc:creator>
		<pubDate>Thu, 13 Mar 2008 13:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart#comment-29</guid>
		<description>The problem with that is that you can&#039;t push to it. Unless you&#039;re working with a bare repo Git will accept your pushes but it won&#039;t commit them. Or, that&#039;s my understanding of it. Yes, you could just keep re-uploading, and over-writing the repo on the server but that seems a crude work-around.</description>
		<content:encoded><![CDATA[<p>The problem with that is that you can&#8217;t push to it. Unless you&#8217;re working with a bare repo Git will accept your pushes but it won&#8217;t commit them. Or, that&#8217;s my understanding of it. Yes, you could just keep re-uploading, and over-writing the repo on the server but that seems a crude work-around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Bronson</title>
		<link>http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/comment-page-1#comment-25</link>
		<dc:creator>Scott Bronson</dc:creator>
		<pubDate>Wed, 12 Mar 2008 18:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart#comment-25</guid>
		<description>This flowchart works for git too.  If you copy a git repo up to your server, you can immediately clone it:

scp -r my-git-project me@example.com:
cd /tmp
git clone http://example.com/my-git-project/.git

I don&#039;t see how that&#039;s any harder than Darcs...?</description>
		<content:encoded><![CDATA[<p>This flowchart works for git too.  If you copy a git repo up to your server, you can immediately clone it:</p>
<p>scp -r my-git-project <a href="mailto:me@example.com">me@example.com</a>:<br />
cd /tmp<br />
git clone <a href="http://example.com/my-git-project/.git" rel="nofollow">http://example.com/my-git-project/.git</a></p>
<p>I don&#8217;t see how that&#8217;s any harder than Darcs&#8230;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
