On Sat, Jan 19, 2013 at 7:42 AM, Karl Heinz Marbaise wrote:
>
> so after thinking about the concept...
> it does not make sense to go further with a shared working copies on a
> network drive there are too many issues (of course, cause SVN is not made
> for such things)..so i will drop the idea...
Karl Heinz Marbaise wrote on Sat, Jan 19, 2013 at 14:42:30 +0100:
> Hi,
>
>> Have you considered other solutions? For example, the ASF CMS maintains
>> one working copy per project, and uses zfs copy-on-write clones to fork
>> off a per-user working copy for each user (even concurrent users) who
>
Hi,
> You'll need to think about permissions: when wc.db is rewritten, or
a new .svn/pristine/ file created, would user2 have permissions to
replace or unlink it (respectively)?
Authz would be a concern too, if the two users' read accesses differ.
(the code should DTRT --- it's no different tha
Karl Heinz Marbaise wrote on Thu, Dec 27, 2012 at 16:03:55 +0100:
> Network: working-copy-1
> User 1 accesses working-copy-1 and changes some files and will checkin
> those changes.
>
> User 2 accesses working-copy-1 and changes some files and will checkin
> those changes.
> etc.
>
> My knowled
On 2012-12-27 16:03, Karl Heinz Marbaise wrote:
> Hi,
>
> i just want to check my assumption by the user/dev community.
>
> I have the following scenario.
>
> From a central SVN server there should be done checkouts (different working
> copies) on a network drive.
> The working copies will be a
