On Jan 15, 2014, at 5:51 AM, Christophe Demarey [via Smalltalk] &lt;<a href="/user/SendEmail.jtp?type=node&node=4737315&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>&gt; wrote:
<br/>&gt; I forgot to answer this one:
<br/>&gt; 
<br/>&gt;&gt;&gt; - I reported before, but Versionner needs a standard repositoryChooser that
<br/>&gt;&gt;&gt; allows to select from known repos or create a new one from a template ( like
<br/>&gt;&gt;&gt; MC Browser, but hopefully better ;) )
<br/>&gt; 
<br/>&gt; I planned to do that friday.
<br/>&gt; I extracted the repository chooser from Komitter to share it with Versionner.
<br/><br/>Great! One place it's needed is when specifying the repository of a dependent project. For example, I loaded BabyMock via the config at MetaRepoFor20, but the main repo is sthub/.../BabyMock. Even though #2 is in the system, because the packages were loaded from there, it doesn't appear on the list - only #1 does. So I had to pick #1 and then copy/paste #2 in later.

	
	
	<div class="signature" style="margin-top:1em;color:#666666;font-size:11px;">
				Cheers,
<br/>Sean
			</div>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://forum.world.st/Strange-Versionner-behavior-tp4736758p4737315.html">Re: Strange Versionner behavior</a><br/>
Sent from the <a href="http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html">Pharo Smalltalk Developers mailing list archive</a> at Nabble.com.<br/>