<html>#367: When a repo URL changes, GetComponents should offer more help
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>GetComponents</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>assignee:</td><td>Roland Haas (was Eric Seidel)</td></tr>
<tr><td>responsible:</td><td>[] (was [])</td></tr>
</table></p>
<p>When a repo URL changes, GetComponents currently suggests to check out the repo from scratch (and presumably delete/ignore the old repo). This is very inflexible, in particular when the user has changes in the old repository, which often happens during development.</p>
<p>SVN (and presumably all other VC software) offer commands to update the URL, so that one can keep the current checkout. Of course, this makes only sense if this is the same repository that only moved to a new URL, but this seems to happen often enough.</p>
<p>GetComponents should at least output instructions for updating the URL.</p>
<p>It would be even better if GetComponents detected that new and old repo are the same, and then update the repo URL by itself.</p>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/367/when-a-repo-url-changes-getcomponents'>https://bitbucket.org/einsteintoolkit/tickets/issues/367/when-a-repo-url-changes-getcomponents</a></p>
</html>