Hi Eric,
You are right, move and commit works with separate working copies and
recent SVN releases. The problem is that I need to maintain
compatibility with SVN 1.6. SVN 1.6 is not able to do that.
Furthermore it would be good to have a simple way to determine the
status. If it is not one working copy then users might miss a piece.
It's not impossible to work with separate working copies, but the
simpler the better. There is more users than administrators, so easy
refers to the users. That's why I'm looking for a way to make it
simpler for administrators too.
Holger
On 07.09.2015 18:29, Eric Johnson wrote:
> Hi Holger,
>
> It is possible to reference two working copies in a single Subversion
> command line operation. For example, you can copy or move from one
> working copy to another.
>
> Eric
>
>> On Sep 7, 2015, at 7:34 AM, Holger Schmidt <Holger.Schmidt_at_zmdi.com> wrote:
>>
>> It should be one working copy to be able to move resources from one
>> leaf to another or to commit changes that affect multiple leaves in
>> one changeset. The leaves belong to one project, so it was a
>> logical choice to have them in one working copy.
>>
>> Regards,
>> Holger
>>
>>
>>> On 07.09.2015 16:20, Eric Johnson wrote:
>>> Why do you need one working copy?
>>>
>>>> On Sep 7, 2015, at 5:31 AM, Holger Schmidt <Holger.Schmidt_at_zmdi.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> There is a repository with this directory tree:
>>>>
>>>> root
>>>> +- dir_a
>>>> +- dir_b
>>>> | +- dir_c
>>>> | +- dir_d
>>>> +- dir_e
>>>> +- dir_f
>>>> +- dir_g
>>>>
>>>> Because there is sensible data in there user usr_u has read/write
>>>> access only to dir_c and dir_g.
>>>>
>>>> Question: How do I configure this with the path based authorization
>>>> (Apache + mod_authz_svn + AuthzSVNAccessFile) and with one working
>>>> copy?
Received on 2015-09-08 12:43:47 CEST