> > Try this workaround:
> > Do a normal windows file search on the common directory without entering
> > any search criteria. This will return all files contained in the
> > directory. You can then select multiple files and commit them.
I've actually tried this one. Unfortunately, the search takes about as
long as a recursive Status scan would, though 1 scan is still better
than the 2-3 we go through now. There's no way to sort or filter the
results by svn status right now, so the manual part of the selection
takes a lot longer, unless some other File Explorer native sort
criteria can be used. Perhaps sort by modified time could be used, in
the general case? Otherwise, the slowing of the manual selection
process here almost defeats any benefit gained, by avoiding the
castrated right-click options of the current TSVN dialogs.
The resulting selection list would be processed faster once
completed, since the same selections can be held through all the Lock,
Update, and Commit steps. In the most problematic (read: big and
diverse) directory trees, it would take too long to sort through the
list manually, but it could still be useful if the search criteria can
be limited in some way pertaining to the commit, like "*.cpp; *.h",
and "newer than xx/xx/xxx".
> Another solution for TortoiseSVN 1.4.0:
> Call "commit" on one file which you want to commit. Then drag further files
> from the windows explorer and drop them on the list of files in the commit
> dialog. These files will then be added. This allows you to commit files of
> different directories without having to call "commit" on their common
> parent directory.
> Please try the release candidate of TortoiseSVN 1.4.0.
This is fine for pre-selecting a commit list without a recursive
Status fetch, but it doesn't help in applying the Update step to the
same list non-recursively. Status refresh on the Commit dialog might
still be slower than necessary, without the non-recursive
directory-intersection logic mentioned earlier in the thread, and in
some cases just as slow as a recursive Status fetch, due to the
problems Stefan described with the current per-file Status fetch
overhead. Still, this might make it worthwhile to check out TSVN
1.4.0RC1, if only for the performance benefit in Commits of file lists
with low parent-folder intersection totals.
Is anyone else beginning to see how much easier things would be if
"update" and "refresh status" right-click options were just added to
the TSVN path-listing dialogs, along with the "keep alive" checkbox on
the Commit dialog? I feel so alone here. I'm willing to bribe
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Aug 11 19:16:02 2006