On Sat, Jul 18, 2009 at 04:10:07PM +0100, Barry Scott wrote:
> On 15 Jul 2009, at 12:37, Stefan Sperling wrote:
>
> > On Wed, Jul 15, 2009 at 08:17:55AM +0100, Barry Scott wrote:
> >> The attached script demonstrates what looks like a bug in subversion.
> >
> > This is not a bug, but desired behaviour.
>
> Ouch.
>
> Its certainly not "desirable" behaviour, but I do understand your
> explanation.
>
> With only one working copy committing to the repos I need to add
> updates to keep working
> thats not intuitive. How long did it take you to figure this out?
Mixed-revision working copies are a normal albeit fairly invisible
phenomenon in Subversion. But they happen every time you commit
something. They are a consequence of Subversion's design.
You can't expect Subversion to update any items to HEAD during
a commit expect those being committed. When the commit is confirmed
by the server, the client can infer the latest state of items
it has just committed, but it has no idea about any other items.
The other items need to be checked for pending updates separately.
And that's what "svn update" is for.
I think the alternative of having unrelated items updated during
a commit would be even more confusing.
Stefan
Received on 2009-07-18 17:32:41 CEST