StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As you indicated that you still want to be able to check out older revisions, the only solution is really to "rewrite" the entire history (solution D mentioned earlier).</p> <p>To do this, you should:</p> <p>1) Dump the contents of the <em>entire</em> repository using <a href="http://svnbook.red-bean.com/en/1.1/re31.html" rel="noreferrer" title="svnadmin dump">svnadmin dump</a>:</p> <pre><code>$ svnadmin dump /path/to/repos > original-dumpfile * Dumped revision 0. * Dumped revision 1. * Dumped revision 2. * Dumped revision 3. </code></pre> <p>2) Edit the dump file, to change the svn:externals URLs. <strong>This is the most difficult part</strong>: Assuming the repository contains binary data as well, opening the dump file in a plain text editor will most likely corrupt the dump file. I've had good experiences using a so-called "hex-editor", for instance the <a href="http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm" rel="noreferrer" title="Freeware Hex Editor XVI32">Freeware Hex Editor XVI32</a></p> <p>3) Create a new repository and load the modified dumpfile into it:</p> <pre><code>$ svnadmin create newrepos $ svnadmin load newrepos < modified-dumpfile </code></pre> <p>For more information, you might also be interested in this link:<br> <a href="http://svnbook.red-bean.com/en/1.1/ch05s03.html" rel="noreferrer">http://svnbook.red-bean.com/en/1.1/ch05s03.html</a></p> <p>NOTE: Subversion 1.5 actually added support for <em>relative URLs</em> in the svn:externals property, which can precisely prevent these sort of problems in the future:<br> <a href="http://subversion.tigris.org/svn_1.5_releasenotes.html#externals" rel="noreferrer">http://subversion.tigris.org/svn_1.5_releasenotes.html#externals</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload