Well, I'm in the same position as Schmidt dude in the post below... and
all because this software that we develop really isn't that easy to
setup, so there is only one working copy, one beta test copy and then
exported production release. And 1.4 made my life as SVN admin a hell on
earth.. once again :)
(I still remember 0.3x days...) Is there anyway around this?
-- Clip from archives --
On Oct 31, 2006, at 2:06 AM, Shakespeare, Simon ((Pensions)) wrote:
>> -----Original Message-----
>> From: Ryan Schmidt [mailto:firstname.lastname@example.org]
>> Sent: 30 October 2006 21:04
>> To: Shakespeare, Simon (Pensions)
>> Cc: Users (E-mail)
>> Subject: Re: Permission problems following upgrade to 1.4
>> On Oct 30, 2006, at 04:37, Shakespeare, Simon (Pensions) wrote:
>>> I'm getting a lot of problems as per below. I'm sure
>> everything works
>>> OK if it was just one user. I'm guessing that the first person to
>>> touch/modify the
>>> working copy has somehow taken the permissions of files that were
>>> in work at the
>>> time the working copy was upgraded i.e. status "M".
>> Why is more than one user attempting to use the same working copy?
>> The usual workflow would be for each user to have their own working
> Hi Ryan - We share working copies & use locking.
> I know this is not the recommended way & causes me big headaches
> but there you go - not my choice.
perhaps it's time to talk to the person who made that silly decision
and point out that locking and shared working copies are at cross
Received on Mon Nov 20 11:03:43 2006