[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SV: Extending TortoiseSVN/Subversion

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2006-07-31 13:14:12 CEST

> We have a *lot* of files and directories in
> our repositories, and NTFS directory-walks
> are painfully slow, so this speeds update
> times a great deal, especially on the LAN.

Just out of curiosity: ~How many files, how many MB?

> Subversion may not be capable of doing the same
> optimizations, because of cross-platform issues.

Subversion always (what I have seen) puts safety first. The method to
find modified files used now guarantees that a commit operation will get
all changed files, as SVN will verify every individual file.
Optimizations that take shortcuts that sacrifices safety will probably
be regarded with scepticism...

> I was thinking of writing a small Shell-Extension
> script, that would detect any file Modify operation
... adds to a list ...
> Any file in the list that is successfully Committed
> would be deleted from the list.

To me this seems like quite specialized requirements. Personally, I do
not think they should be a core part of TSVN.

However: There's a long time standing issue in our issue-tracker
regarding hooks for TSVN. I guess your ideas (as a separate program)
could be integrated with TSVN quite nicely if such a feature was

Maybe that would be a good place to start?

> This would be something I try to integrate into
> TortoiseSVN, to alter the Commit GUI with Change-List
> selection and naming options. Would this be allowed?

Everything that clutters the GUI even more is usually frowned upon. But
share your specific ideas with the mailing list and check out the

> My users don't care if the files they are Committing are not
> up-to-date, as long as there are no merge conflicts.

Maybe they should care?

> They are also annoyed by the occasional collision,

Communication. Its importance can not be overstated. Lack of it does not
only lead to annoyances but also to (double) wasted work. Not good. You
can't solve this by writing scripts, you actually have to talk to each

> I would like to make a different "Commit" for these
> users, that does all these tasks, in this order,
> for all files:
> Lock, Update, check for conflicts and resolve them,
> and last Commit all.

Why? I cannot see the point of doing this. Maybe you should have a look
at svn:needs-lock?

> What would be the policy on such a change, to
> TortoiseSVN command definitions?

Probably a NO right away. But I'm just guessing here. :-)


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jul 31 13:14:01 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.