Re: Bug Report: Revision doesn´t update in working copy after making a commit

Asier Ibarra (Ingeteam Traction) wrote:

[...]
>
> I think the problem is that *after doing commit, the revision number
> in the working copy doesn't get updated*.
>
> That's why tortoise thinks I'm branching from revision 1 when I am
> really up to date with revision 5.
>

Hello Asier Ibarra,

I think I understand your explanation, but isn't the issue that you
assumed that (being the only contributor) any commits from you would
raise the revision number of the working copy?

But why should that be the case?

SVN cannot know that you are the only contributor without extra steps to
find out whether the working copy is actually at HEAD, and if it isn't
(because someone else committed something too) it would have to - after
the commit - perform an update or inform you that the revision stayed
the same this time because someone else also committed something - so
that you make no (incorrect) assumptions on what revision your working
copy is at.

(And if you then forget about what your latest commit made the revision
of your working copy to, you will branch at the "wrong" revision, just
like you did in your example.)

(Personally, I like to work directly on the server for such stuff, via
the repo-browser, that way I wouldn't have run into this problem.)

With best regards

Clemens Anhuth

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1138624

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-11 13:12:22 CET