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

Re: Feature Request: Option to *always* commit all the changes in the *entire* working copy.

From: Clemens Anhuth <clemens_at_froglogic.com>
Date: Tue, 04 Aug 2009 14:57:00 +0200

Nick Sabalausky wrote:
> I realize not every corner case can or should always be covered by a
> program, but I have a very difficult time believing that I'm anywhere
> remotely near being the only one who wants to do a full commit 99% of the
> time. Even an optional warning (as someone else very astutely suggested) for
> whenever there are unselected changes in the commit dialog would be
> perfectly satisfactory, and would perhaps be a sufficiently
> generally-acceptable approach to satiate the naysayers and warrant inclusion
> in TSVN.

It is up to you to prove that it is a common enough case.

Scripts aren't hacks. Scripts are the reason why productive work is
possible in countless cases in the first place.

They are exactly for cases like this, where there is no common agreement
about a mode or feature and but where the task can be accomplished by
scripting (see

Another approach could be to have a client-side start-commit hook
scripts which aborts if you try to commit on a directory whose parent
directory doesn't have a .svn folder. This approach would admittedly
serve to educate the user however.

With best regards

Clemens Anhuth

www.froglogic.com - Squish - Multi-Platform GUI Testing
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-04 14:58:48 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.