<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 23, 2014 at 3:17 PM, Peter Soetens <span dir="ltr"><<a href="mailto:peter@thesourceworks.com" target="_blank">peter@thesourceworks.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">I'm proposing to leave gitorious as well for the Orocos Toolchain and<br></div>
related libraries...<br></blockquote><div>Yes .. I knew you would be happy about that one ;-)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It would boil down to changing the installation instructions and<br>
changing the bootstrap links to what exists on github and to reverse<br>
the synchronisation scripts, ie, force-sync from github to gitorious.<br></blockquote><div>In the Rock case, the plan was to drop gitorious completely. This is transparent to both developers and users as autoproj will update the git push/pull URLs.</div>
<div><br></div><div>Sylvain</div></div></div></div>