Paul Skiter wrote:
> SteveKing <steveking <at> gmx.ch> writes:
>
>
>>That's not quite right. Even 'svn commit' will give you the same error
>>message if you do an 'svn commit -N' (non-recursive commit).
>>If you don't want to have that error message, simply don't uncheck any
>>files/folders shown in the commit dialog - then TSVN will do a recursive
>>commit too and it will work as you want. But as soon as you deselect one
>>or more items from the commit dialog, TSVN *has* to do a non-recursive
>>commit, and then it will fail in that case.
>
>
> I do *not* uncheck anything shown in the commit dialog. All checkbox are
> checked. I simply write a message and press OK... and get the error.
Ok, I can see now what you mean. Took me quite a while to find out why
TSVN behaves differently than the CL client or RapidSVN.
Bottom line is this: you can either use TSVN and have the ability to
deselect files and folders from committing, or use the other clients
which don't support that (or not as reliable as TSVN). With TSVN you can
be sure that *nothing* you haven't explicitely selected get's committed.
And because TSVN does that, it can't commit a folder which is deleted
outside Subversion. To do that, we would have to commit the *parent*
folder of that deleted folder, and that would mean a risk to commit
something else you didn't wanted to.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 2 19:40:28 2005