﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Bug Hunting Story</title><description>You only need one SvnBridge, it does not require anything else.
  
The SvnBridge instance can access any server that you use
</description><link>http://ayende.com/3344/bug-hunting-story#comment2</link><guid>http://ayende.com/3344/bug-hunting-story#comment2</guid><pubDate>Wed, 04 Jun 2008 08:33:54 GMT</pubDate></item><item><title>Taras commented on Bug Hunting Story</title><description>Oren, i'm using SvnBridge since the dawn ot time to periodically fetch some dozens of codeplex projects. Meanwhile, i've got a habit to create a .bat file for each to spawn a svnbridge with an url. Once i've realised that url pattern revolves around something like [https://tfs0{n}.codeplex.com], so reduced the number of .bats, incorporating project name into .bat name in a comma-separated list. Still this matter of things buggs me..
  
  
Could you please tell, what in your opinion is a clean way to keep some dozens svnbridge configurations ?
</description><link>http://ayende.com/3344/bug-hunting-story#comment1</link><guid>http://ayende.com/3344/bug-hunting-story#comment1</guid><pubDate>Wed, 04 Jun 2008 08:23:20 GMT</pubDate></item></channel></rss>