On Wed, May 18, 2011 at 3:19 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 17.05.2011 04:40, Daniel Becroft wrote:
> > Hi,
> >
> > 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'm assuming this is not intentional.
>
> Unfortunately, it is.
>
> Here's why:
> 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.
>
I was more questioning whether we need to individual status line, not
necessarily
that each item is updated explicitly. However, I just checked the
command-line
client, and it does the same thing. Has this changed recently?
> Question is: should I change that?
> This is of course up for discussion...
The CI purist in me says everything should be updated, the problem here is
what level do you update. Lowest common parent, perhaps? Then again, I
guess the workflow should be to explicitly update outside of the commit
process anyway, run the build/unit tests, and then commit.
I don't have any preference either way - just thought the multiple
notifications
thing looked a bit strange.
Cheers,
Daniel B.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2739458
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-17 23:05:23 CEST