·Imhotep·;7026155 said:
The TortoiseSVN export command doesn't delete files that are marked for deletion in the SVN. So you have to do it manually...
Hmm, I thought I had already explained this. The reason SVN Export does not delete removed files is because export has no knowledge that you ever got the deleted file in the first place. That may sound goofy, so let me explain in reverse.
Think of SVN as a big cash register tape tracking file operations: add, update, and delete. Every operation is numbered for tracking.
Code:
1: Add a.txt - "This is file A"
2: Add b.txt - "This is file B"
3. Update a.txt - "Now this is A"
4. Add c.txt - "This is file C"
5. Delete b.txt
When you do SVN Checkout, it essentially performs the same operations on your hard drive and remembers the number (revision) of the last operation.
In the above example, if you had done a Checkout at revision 2, you would get both a.txt and b.txt and a marker saying "revision 2":
Code:
svn checkout
A a.txt
A b.txt
2 Added
At revision 2
When you do SVN Update, it uses this revision number stored on your hard drive to ask SVN for all of the operations that have occurred since that number. It knows to delete files only because it remembers that it told your computer to add a file earlier.
To continue the example:
Code:
svn update
*** to SVN server: I am at 2 ***
U a.txt
A c.txt
D b.txt
1 Added
1 Updated
1 Deleted
At revsion 5
However, SVN Export doesn't use any local revision tracking, so it doesn't know that you had gotten b.txt previously. When you issue the export command, it takes a snapshot of the current state of the repository and sends it to your computer.
If a file was added and later deleted, it doesn't bother to send the file to your machine.
Bottom line: Do not try to update using SVN Export.
Either use Export into a new, empty directory or use SVN Checkout to start and SVN Update to get the latest changes since the last checkout/update.
I hope that clears it up.
I'm using the 3.0 version with 3.17 and I found the logger doesn't work
I have left all option to default as always.
The logger was changed and the defaults set up so that logging isn't automatic. Go into the Logging tab of the BUG Options screen and check "Silent Start". Also, make sure "Enabled" is checked, but it should be by default.
Previously, just being Enabled would log all games. This defeated the purpose of Silent Start, so we changed it.
I missed that reply. Enabling silent start was the solution. But it's not clear for me why the non-silent version hasn't started. Should it pop up a dialog asking which file should be the log going in? It didn't.
keep up the good work 
