<?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: SVN Scripts and Tools</title>
	<atom:link href="http://alexking.org/blog/2008/01/12/svn-scripts-and-tools/feed" rel="self" type="application/rss+xml" />
	<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools</link>
	<description>Alex King, Denver Web Developer</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:02:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Javier Linares</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60959</link>
		<dc:creator>Javier Linares</dc:creator>
		<pubDate>Wed, 23 Jan 2008 19:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60959</guid>
		<description>Exactly, Alex, I prefer a digest of all changes than a message per commit. And if I&#039;m on a trip, I just want  the digest when I switch on my laptop.

Jose, we also thought in something like the solution you propose. But we have the feeling that something like that would make our repository huge and every day the percentage of relevant information would decrease. And, although I know permissions per directory are possible, we like how simple permissions to developers based on repositories are.

But, anyway, this is just my solution. Not a perfect one at all. :)</description>
		<content:encoded><![CDATA[<p>Exactly, Alex, I prefer a digest of all changes than a message per commit. And if I&#8217;m on a trip, I just want  the digest when I switch on my laptop.</p>
<p>Jose, we also thought in something like the solution you propose. But we have the feeling that something like that would make our repository huge and every day the percentage of relevant information would decrease. And, although I know permissions per directory are possible, we like how simple permissions to developers based on repositories are.</p>
<p>But, anyway, this is just my solution. Not a perfect one at all. <img src='http://alexking.org/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David O'Shea</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60811</link>
		<dc:creator>David O'Shea</dc:creator>
		<pubDate>Wed, 16 Jan 2008 02:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60811</guid>
		<description>I would have thought that this would work:

svn st ~/src/repo-[123]

At least, I have been able to run &#039;svn status&#039; with more than one working copy listed on the command line when they were all from the one repository; I don&#039;t know if there is some special rule saying that you can&#039;t do this if they are from different repositories.

Also, given that Alex mentioned e-mail notifications, let&#039;s not forget that Warehouse (and also other web front-ends such as WebSVN) allow you to subscribe using RSS.  I haven&#039;t used this myself but one of my co-workers tracks changes this way.</description>
		<content:encoded><![CDATA[<p>I would have thought that this would work:</p>
<p>svn st ~/src/repo-[123]</p>
<p>At least, I have been able to run &#8216;svn status&#8217; with more than one working copy listed on the command line when they were all from the one repository; I don&#8217;t know if there is some special rule saying that you can&#8217;t do this if they are from different repositories.</p>
<p>Also, given that Alex mentioned e-mail notifications, let&#8217;s not forget that Warehouse (and also other web front-ends such as WebSVN) allow you to subscribe using RSS.  I haven&#8217;t used this myself but one of my co-workers tracks changes this way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60807</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60807</guid>
		<description>Ooh, that&#039;s clever.</description>
		<content:encoded><![CDATA[<p>Ooh, that&#8217;s clever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Hildebrand</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60805</link>
		<dc:creator>Joe Hildebrand</dc:creator>
		<pubDate>Tue, 15 Jan 2008 17:29:10 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60805</guid>
		<description>Why don&#039;t you set up a local svn repository, which just has a top level root, and put externals in for all of the projects you want to track?  One &quot;svn up&quot;, and you&#039;re home.</description>
		<content:encoded><![CDATA[<p>Why don&#8217;t you set up a local svn repository, which just has a top level root, and put externals in for all of the projects you want to track?  One &#8220;svn up&#8221;, and you&#8217;re home.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60778</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 14 Jan 2008 15:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60778</guid>
		<description>Interesting, why not just set up SVN e-mail notifications? Perhaps you just want a &quot;digest&quot; of the changes?</description>
		<content:encoded><![CDATA[<p>Interesting, why not just set up SVN e-mail notifications? Perhaps you just want a &#8220;digest&#8221; of the changes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Javier Linares</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60767</link>
		<dc:creator>Javier Linares</dc:creator>
		<pubDate>Mon, 14 Jan 2008 09:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60767</guid>
		<description>I have the same functionality to do &quot;svn update&quot; in all repositories, but I&#039;ve made it a little more complex. We create a repository for each project and department in our company and that means more than 20 active repositories. So I find very useful to receive every morning a summary of changes and updates.

&lt;a href=&quot;http://javierlinares.com/files/svnupdate.sh.txt&quot;&gt;Here you have a copy&lt;/a&gt;.  The idea is just to save the changes in a log file and then mail it to me with a custom format. That way if someone makes a little change in one svn, I can see it next morning.</description>
		<content:encoded><![CDATA[<p>I have the same functionality to do &#8220;svn update&#8221; in all repositories, but I&#8217;ve made it a little more complex. We create a repository for each project and department in our company and that means more than 20 active repositories. So I find very useful to receive every morning a summary of changes and updates.</p>
<p><a href="http://javierlinares.com/files/svnupdate.sh.txt">Here you have a copy</a>.  The idea is just to save the changes in a log file and then mail it to me with a custom format. That way if someone makes a little change in one svn, I can see it next morning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecosystems &#187; links for 2008-01-14</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60760</link>
		<dc:creator>tecosystems &#187; links for 2008-01-14</dc:creator>
		<pubDate>Mon, 14 Jan 2008 05:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60760</guid>
		<description>[...] SVN Scripts and Tools &#124; alexking.org looks like Crowd Favorite hasn&#8217;t gotten the DVCS religion yet (tags: howto svn crowdfavorite subversion dvcs) [...]</description>
		<content:encoded><![CDATA[<p>[...] SVN Scripts and Tools | alexking.org looks like Crowd Favorite hasn&#8217;t gotten the DVCS religion yet (tags: howto svn crowdfavorite subversion dvcs) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deuce</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60753</link>
		<dc:creator>Deuce</dc:creator>
		<pubDate>Sun, 13 Jan 2008 19:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60753</guid>
		<description>You could launch TextMate from the command line just using &quot;mate&quot; instead.  So your line: &quot;open -a TextMate ~/Desktop/svn-status.txt&quot; could just be &quot;mate ~/Desktop/svn-status.txt&quot;. If it doesn&#039;t work, then it ln wasn&#039;t made on install of TextMate, and you can fix it with these instructions: 
http://macromates.com/textmate/manual/using_textmate_from_terminal

Though SVN may not be the most perfect solution, I have definitely come to appreciate it, and version control in general.  It saves lives in a very painless way.

Hope its helpful!</description>
		<content:encoded><![CDATA[<p>You could launch TextMate from the command line just using &#8220;mate&#8221; instead.  So your line: &#8220;open -a TextMate ~/Desktop/svn-status.txt&#8221; could just be &#8220;mate ~/Desktop/svn-status.txt&#8221;. If it doesn&#8217;t work, then it ln wasn&#8217;t made on install of TextMate, and you can fix it with these instructions:<br />
<a href="http://macromates.com/textmate/manual/using_textmate_from_terminal" rel="nofollow">http://macromates.co[...]rom_terminal</a></p>
<p>Though SVN may not be the most perfect solution, I have definitely come to appreciate it, and version control in general.  It saves lives in a very painless way.</p>
<p>Hope its helpful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60735</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 13 Jan 2008 03:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60735</guid>
		<description>I remember the transition myself, glad you&#039;re already seeing the benefits!</description>
		<content:encoded><![CDATA[<p>I remember the transition myself, glad you&#8217;re already seeing the benefits!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jharr</title>
		<link>http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60728</link>
		<dc:creator>jharr</dc:creator>
		<pubDate>Sun, 13 Jan 2008 02:34:42 +0000</pubDate>
		<guid isPermaLink="false">http://alexking.org/blog/2008/01/12/svn-scripts-and-tools#comment-60728</guid>
		<description>Thanks for these handy little scripts Alex. As a somewhat reformed GUI-SVN user, I have to say getting a handle on SVN in the terminal makes life much easier.  If you&#039;re a designer and you haven&#039;t taken that leap yet, I&#039;d say now&#039;s the time.  As part of that process you quickly learn that aliasing in the .profile is a huge help.</description>
		<content:encoded><![CDATA[<p>Thanks for these handy little scripts Alex. As a somewhat reformed GUI-SVN user, I have to say getting a handle on SVN in the terminal makes life much easier.  If you&#8217;re a designer and you haven&#8217;t taken that leap yet, I&#8217;d say now&#8217;s the time.  As part of that process you quickly learn that aliasing in the .profile is a huge help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

