[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: Nick Sabalausky <business4_at_semitwist.com>
Date: Tue, 4 Aug 2009 07:08:05 -0400

clackwell Full name Clemens Anhuth Date 2009-08-03 22:38:33 PDT
> Have you considered having a script for committing?

As I said in another post yesterday, yes, I have considered that, and I will
need to do that, but I don't want to have to use that as a permanent

> You can hook that into the context menu of all folders if you like. You
> could also move the Commit entry from TSVN back into the TSVN sub-menu of
> the folder context menu, to avoid accidentally using that.


>I am not sure this kind of case should be generalized and be tackled by
>TSVN itself. Because if you start assuming this kind of incorrect usage,
>there is no end to obscuring and bloating the TSVN source code base with
>exceptions and handlers for any possible misuse. But philosophically it is
>nice to think of a software that tries very hard to make its users happy of
>course. :)

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.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-04 13:12:35 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.