Seumas Soltysik writes:
> I am still a bit confused about the difference between --steal-lock and
> --disable-locking. I understand that --steal-lock basically deletes/steals
> the lock property on revision 0 which controls who has the right to perform
> an svnsync. I use this in the event that a
39: User '' does not own lock on path '/foo/bar'
> >
> > I understand why this is happening but I am not sure what the solution
> is.
> >
> > Based upon the svnsync documentation it would appear that the "svnsync
> > --disable-locking&quo
tion is.
>
> Based upon the svnsync documentation it would appear that the "svnsync
> --disable-locking" option is what I need. However, in my opinion the
> documentation is unclear about what the option does and googling returns
> very little that is helpful.
> Am I
it would appear that the "svnsync
--disable-locking" option is what I need. However, in my opinion the
documentation is unclear about what the option does and googling returns
very little that is helpful.
Am I correct in believing that the --disable-locking mechanism will ignore
all user lo
