[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: Todd C. Gleason <tgleason_at_impac.com>
Date: Mon, 3 Aug 2009 13:41:09 -0700

> -----Original Message-----
> From: Nick Sabalausky [mailto:business4_at_semitwist.com]
> Sent: Monday, August 03, 2009 2:11 PM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Feature Request: Option to *always* commit all the
changes in
> the *entire* working copy.
> "Werner F dot Bruhin" <werner dot bruhin at free dot fr> Full name
> F dot Bruhin" <werner dot bruhin at free dot fr> Date 2009-08-03
> >
> >What about creating a simple script which calls svn command line to
> commit
> >project x from its top folder?
> I didn't want to have to resort to a hack like that, but since my idea
> seems
> to be getting met with nothing but outright dismissal and accusations
> clumsiness/laziness/"it's all your fault"/etc it looks like I'll have

If I can add another perspective, I wouldn't mind a system where at
least TSVNCache fed info into (I think) TortoiseProc such that when you
went to commit, and had not selected a sufficient "root" of all changes
in your WC, that it would give you a warning of some sort.

In my company, people routinely don't commit at the root, because it can
take a few (3-5) minutes to scan the entire WC. This leads to incorrect
commits (which I would not personally describe as "corruption", but
that's a matter of opinion). Some also split things into multiple
commits because they see it as faster or easier or whatnot. Now this is
a training issue, but I hope that a future version of Subversion and
TortoiseSVN make it so quick to detect and commit all changes, that it
unarguably takes longer to make multiple commits than to commit from the

For what it's worth, I suggested some things related to this in a
conversation at
rowseAll&dsMessageId=1267185#messagefocus . Potentially some of them
will be in Subversion 1.7 or in the near term afterward. It would be
very nice if TortoiseSVN was optimized against whatever Subversion 1.7
may offer. Honestly, I wouldn't mind if TortoiseSVN could use its
TSVNCache data to let you commit everything that TSVNCache knows is
"dirty" rather than forcing the file scan.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-03 22:41:39 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.