<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Comparison of Configs/Aliases in Bazaar, CVS and  Subversion</title>
	<link>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/</link>
	<description>Random stuff</description>
	<pubDate>Mon, 07 Jul 2008 01:14:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Erich Schubert</title>
		<link>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-35</link>
		<dc:creator>Erich Schubert</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-35</guid>
		<description>Hi, since you apparently are quite an expert on revision management - do you have a hint for my "CoW" problem?&lt;br/&gt;Basically I'd like to have copy-on-write branches.&lt;br/&gt;Meaning that I want files by default to follow the trunk branch, only if I modify the file it gets "locked" to the current branch. So that by running "foo update" I get all the updates, except for where I decided to diverge?&lt;p/&gt;using svn:externals was suggested to me, but it doesn't do the trick, I need it on a per-file basis. And I'd like to have it automatically, so I can just commit my changes and they'll end up in my "overlay" repository by default...&lt;p/&gt;Two blog entries, where I asked for advice for this usage:&lt;br/&gt;&lt;a href="http://blog.drinsama.de/erich/en/linux/2005082601-server-management.html"&gt;http://blog.drinsama.de/erich/en/linux/2005082601-server-management.html&lt;/a&gt;&lt;br/&gt;&lt;a href="http://blog.drinsama.de/erich/en/linux/2005082501-revision-management.html"&gt;http://blog.drinsama.de/erich/en/linux/2005082501-revision-management.html&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hi, since you apparently are quite an expert on revision management - do you have a hint for my &#8220;CoW&#8221; problem?<br />Basically I&#8217;d like to have copy-on-write branches.<br />Meaning that I want files by default to follow the trunk branch, only if I modify the file it gets &#8220;locked&#8221; to the current branch. So that by running &#8220;foo update&#8221; I get all the updates, except for where I decided to diverge?
<p />using svn:externals was suggested to me, but it doesn&#8217;t do the trick, I need it on a per-file basis. And I&#8217;d like to have it automatically, so I can just commit my changes and they&#8217;ll end up in my &#8220;overlay&#8221; repository by default&#8230;
<p />Two blog entries, where I asked for advice for this usage:<br /><a href="http://blog.drinsama.de/erich/en/linux/2005082601-server-management.html">http://blog.drinsama.de/erich/en/linux/2005082601-server-management.html</a><br /><a href="http://blog.drinsama.de/erich/en/linux/2005082501-revision-management.html">http://blog.drinsama.de/erich/en/linux/2005082501-revision-management.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-36</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-36</guid>
		<description>With Bazaar, the way you'd handle this would be by branching the upstream.  Now rather than running "update", you'd "merge" from the upstream branch, fix conflicts (if there are any), and "commit".&lt;p/&gt;To see what your local changes are, just diff your branch against the upstream one.&lt;p/&gt;This is not quite the same as you asked for, since you will get updates to files you have modified (hence the possibility of conflicts on merge).  However, this is usually considered a better system, since using some files from one version and other files from another version could easily cause problems.</description>
		<content:encoded><![CDATA[<p>With Bazaar, the way you&#8217;d handle this would be by branching the upstream.  Now rather than running &#8220;update&#8221;, you&#8217;d &#8220;merge&#8221; from the upstream branch, fix conflicts (if there are any), and &#8220;commit&#8221;.
<p />To see what your local changes are, just diff your branch against the upstream one.
<p />This is not quite the same as you asked for, since you will get updates to files you have modified (hence the possibility of conflicts on merge).  However, this is usually considered a better system, since using some files from one version and other files from another version could easily cause problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Kelley</title>
		<link>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-37</link>
		<dc:creator>Sean Kelley</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-37</guid>
		<description>Very interesting.  I've not used CVS since University.  I must confess that in my job I've been using Borland's StarTeam and love it.It is really hard to go back to the command line again.&lt;p/&gt;Sean</description>
		<content:encoded><![CDATA[<p>Very interesting.  I&#8217;ve not used CVS since University.  I must confess that in my job I&#8217;ve been using Borland&#8217;s StarTeam and love it.It is really hard to go back to the command line again.
<p />Sean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fraggle</title>
		<link>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-38</link>
		<dc:creator>fraggle</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/jamesh/2005/08/29/comparison-of-configsaliases-in-bazaar-cvs-and-subversion/#comment-38</guid>
		<description>Sounds like incredibly useless and confusing functionality and that a common shared library would be a much better solution.</description>
		<content:encoded><![CDATA[<p>Sounds like incredibly useless and confusing functionality and that a common shared library would be a much better solution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
