[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Branching Questions

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 1 Jul 2011 09:57:19 -0400

Please stop top-posting. The convention on this mailing list is to
bottom- or inline-post, and quote the relevant portions you're
responding to.

On Fri, Jul 1, 2011 at 09:43, Phil Pinkerton <pcpinkerton_at_gmail.com> wrote:
> Interesting,
>
> Can you (or anyone else) provide a few scenario examples from your
> experience (not related to horses and besides those given in the
> svnbook.red-bean)?

What are you looking for, exactly?

If you need to restrict all access to a path, including read access,
then you need to use Subversion's built-in path-based authorization or
possibly some Apache configuration tweaks. The links you were given
describe this very well - it's up to you to read & understand how they
apply to your environment.

If you need to restrict write access, you can use path-based
authorization or a hook script. One script commonly used for this is
svnperms.py svnperms.py requires more setup, but allows for wildcards
and finer-grained control.

If you're asking someone to show you a reference implementation,
everyone's implementation of access control is a little different;
it's best if you understand *how* it works and then how you can apply
it to your environment.

> On 7/1/2011 8:11 AM, Tony Sweeney wrote:
>>
>> Sorry, that's a common British idiom which obviously doesn't travel.
>> Racehorses vary in strength, speed, stamina and temperament; some race
>> horses do better in "heavier going" (i.e. a softer, muddier track), some
>> race faster on a dry course, and of course racecourses vary in length.
>> So there's no single answer to "which is the best horse", as there are
>> "horses for courses".  Makes sense now?  Which approach you take to (3)
>> depends on the existing customer set up.  There are a number of
>> tradeoffs, so there's no single right answer.
>>
>> Tony.
>>
>> -----Original Message-----
>> From: Phil Pinkerton [mailto:pcpinkerton_at_gmail.com]
>> Sent: 01 July 2011 12:45
>> To: Tony Sweeney
>> Cc: Subversion User List
>> Subject: Re: Branching Questions
>>
>> Thanks for the quick response.
>>
>> However I have no clue what you mean by Horses for courses.
>>
>> and I certainly cannot reply to my clients question with such an answer.
>>
>> On 7/1/2011 7:03 AM, Tony Sweeney wrote:
>>>
>>> -----Original Message-----
>>> From: Phil Pinkerton [mailto:pcpinkerton_at_gmail.com]
>>> Sent: 01 July 2011 11:58
>>> To: Subversion User List
>>> Subject: Branching Questions
>>>
>>>
>>> 1. We are creating branch out of previous branch, if we want to delete
>>> a old branch or archive it how it will impact the current branch ?
>>>
>>> It won't
>>>
>>> 2. There is no limit on number of branches you can create, is this
>>> true ?
>>>
>>> Effectively.
>>>
>>> 3. What is the best way to lock the Trunk so only certain users can
>>> access it, using Hook Script or using admin tool?
>>>
>>> Horses for courses.
>>>
>>>
>>> Phil
>>>
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the MessageLabs Email Security System.
>>> For more information please visit http://www.messagelabs.com/email
>>> ______________________________________________________________________
>>>
>>> -----
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 10.0.1388 / Virus Database: 1516/3736 - Release Date:
>>> 06/30/11
>>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email
>> ______________________________________________________________________
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 10.0.1388 / Virus Database: 1516/3736 - Release Date: 06/30/11
>>
>
Received on 2011-07-01 15:58:32 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.