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

RE: Update after failed commit updates each file individually

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: Wed, 18 May 2011 08:00:52 +0000

>> I've just tried choosing "Update" after the "working copy is out of date
>> - would you like to update?" option during a commit. For some reason, it
>> shows an "Updating" and "Completed At revision: x" pair for each file I
>> selected during the commit.
> I usually get the "out of date" error because of a property change on a
> folder. Now if TSVN would update the folder you selected for commit, it
> would update everything. And that might not be what you want. You might
> want to only update what's preventing the commit - there might be
> changes in the repository which you're not ready yet to include in your
> working copy.


> Question is: should I change that?
> This is of course up for discussion...

I would argue that in most cases you should do the update on the entire folder. If you get updates that you are not ready for, your changes are probably not ready to be committed either.

To me it feels very unsafe to only update the changed files. It sort of bypasses the lovely update-test-commit safety when files that the changed files may be dependent on are not updated.

So. I would say: Preferably update the entire folder by default.

As an alternative we could leave it up to the user by presenting the choices "Update everything", "Update affected files" and "Don't update".



To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-18 10:01:05 CEST

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

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