SteveKing <steveking <at> gmx.ch> writes:
> 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.
At last I see that you mean too.
TSVN never performs recursive commit, but separately commits every item listed
in the commit dialog's grid. And SVN can't commit non existing paths.
IMO, there are two solutions. The best is to fix SVN itself. If an entry is
missing, but is presented in the parent's '.svn', then it should be committed as
deleted.
The second way is to change TSVN's commit dialog a bit. The dialog has 'Commit
to' field, but has no 'Commit from' field. The field would be useful in any way.
Commit from ....... [ ] Recursive
Checking 'Recursive' checkbox disables item list.
Note that it may be checked by default, because it takes a rather long time to
build committed item list for large folder tree. If user needs items he shall
uncheck the checkbox.
Regards, Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue May 3 10:20:42 2005