[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 17:49:47 -0400

Greywolf <greywolf at starwolf dot com> Full name Greywolf <greywolf at
starwolf dot com> Date 2009-08-04 13:59:41 PDT:
>This is precisely what the "Cancel" button is for: "Hey, where's all the
>other stuff I changed? Oops. Checking in from the wrong spot. Try again..."

There is absolutely no reason why I should have to babysit TSVN when all I
want to do is "Commit all changes in the entire WC". Which actually leads me
to yet another alternate suggestion that'll most likely just get completely
dismissed: "SVN Commit Entire Working Copy...".

>Think of it this way: If you're in a very high-level directory and you,
>say, type "rm -r ./somedir". It is not going to warn you that you are
>potentially removing a lot of stuff and/or a lot of potential state. It
>is going to go off and do it and only give an error if it encounters
>something it cannot handle (read-only directory, segmentation fault after
>removing libc.so, etc.). Whose fault is it that you typed in the wrong
>thing at the wrong place?

"rm" is notorious for having a bad interface, even by Unix standards.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-05 07:15:26 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.