On 9/12/06, David Poole <email@example.com> wrote:
> I'm having a problem with my subversion installation. We're using ssh on
> a OS X server to authenticate users, and the repositories are on the
> same server. My problem is that the server isn't correctly generating
> 'out of date' errors. Example: user Dave and user Joe check out the
> project Bus at revision 42. Dave updates and commits changes to
> plan.php, so the revision is now at 43. Joe modifies a bunch of files,
> including the now out of date plan.php. When he commits, he does not
> update his working copy, and the repository merges all changes,
> including the changes to plan.php, to revision 44. Dave's modifications
> are now in repository limbo. I can get to them, and merge them back into
> the working copies, but I need to have the out of date errors when
> someone tries to update out of date copies.
> If somebody could please help me figure out what's going on, and how to
> fix the out of date (lack of) errors, I'd be very appreciative.
Can you provide a command-line receipe to reproduce?
Received on Wed Sep 13 03:21:36 2006
This is an archived mail posted to the Subversion Users