Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Any change you make to the repo needs a commit, so yes after doing <code>svn delete</code> you need to <code>svn commit</code>. Similarly when you add files, that's a change that needs to be committed. In both cases it's possible to undo the add and delete without commiting.</p> <p>In terms of adding and removing files in one transaction, again that "just works", you'd effectively issue:</p> <pre><code>svn delete C.cpp svn add D.cpp svn commit </code></pre> <p>If you want to recover a deleted file, then you can just recover the file from an earlier revision of the svn repo, then recommit (see also <a href="https://stackoverflow.com/questions/490522/what-is-the-correct-way-to-restore-a-a-deleted-file-from-svn">What is the correct way to restore a deleted file from SVN?</a>). </p> <p>The main thing you must remember though when deleting files: you <strong><em>must</em></strong> delete it using subversion tools (i.e. from the command line as <code>svn delete</code> or using Delete within TortoiseSVN. Just deleting it using <code>del</code>, <code>rm</code>, or a file manager like windows explorer will have SVN see the file as "<em>missing</em>" and not "<em>deleted</em>", and a commit of the repo will not commit the delete; thus the next time you update your working copy, the missing files will be restored. Thus you use subversion to delete the file so subversion knows that you do actually want it deleted.</p> <p>For your last question -- what version of SVN and how big is the repo (in terms of file-count). Essentially T-SVN has to walk the tree and check each file against the repo-version to see it it's changed. As of SVN 1.7, the working copy format changed with a lot of metadata being held in the database, and improvements to the storage of pristine copies (i.e., what the file looked like when it came out of svn) means that it's faster than it was. If you aren't using 1.7, then it's worth checking out. Also, if you have a large repo but only work in a small part of it then consider using sparse checkouts to reduce the size of your local working copy. See <a href="https://stackoverflow.com/a/122291/130352">this answer</a> to <em>Checkout one file from Subversion</em> for a brief overview or sparse checkouts.</p>
 

Querying!

 
Guidance

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