Hi,
we have a trunk and several branches (each branch represents a new
version of our software). We have one computer where we built these
versions, so the last few branches are checked out on this computer.
The workflow to reproduces the problem goes like this:
1. some developer needs to fix a bug in an existing version. So he
does the coding, commits his changes in the trunk.
2. Then he goes to our "build server" (the one computer where we build
versions) and merges his changes into the target branch working copy.
3. Afterwards he commits this changes into the branch.
But this last step (committing the changes into the branch) often
fails with a message that he first needs to update the working copy
because it is out of date.
But updating the working copy seems to do nothing (no new files, no
updates,...) but afterwards the commit succeeds.
Right now it seems that the revision of the checked out working copy
(=branch) is compared to the revision of the whole repository (and NOT
the revision of this specified branch in the repository as one would
expect).
I'm pretty sure about this because I looked up the revision number of
the working copy (context menu, settings, subversion tab) when the
error message shows. After an update (which seems to do nothing) the
revision number is the same as the one of the complete repository.
This can't be right because as soon as anyone commits something in ANY
branch now we need to update the working copy before we can commit any
changes on this computer.
Can anyone please help?
Thanks in advance,
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-01 20:10:09 CEST