From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: overseers@sources.redhat.com
Subject: Re: Controlling cvs commit access
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20001016194459.B3344@cygnus.com> (raw)
In-Reply-To: <20001014002746.A5942@shell17.ba.best.com>
On Sat, Oct 14, 2000 at 12:27:46AM -0700, Jason Molenda wrote:
>We have a large engineering organization at Yahoo with a wider
>variety of cvs uses than I'd seen before. I needed some fine-grained
>way of controlling access to parts of the repository, so I wrote
>a nice little access control list script. It lets you express
>things like
>
> User FOO may only check in changes in directory BAR
>
> Only users FOO, BAR, and BAZ may check in changes in directory BOO
>
> User MOO may not check in any changes to BOO
>
>And all the other variants I could think of as being useful. There
>is a simpler access control script included in the cvs contrib dir
>(cvs_acls.pl), but it sacrifices the expressiveness that my script
>has for much greater simplicity of implementation.
>
>I don't know if this thing would be useful to anyone outside Yahoo,
>but if, for instance, there was ever a hope of merging
>gcc/gdb/binutils/newlib/etc and people were concerned about
>controlling commit policy, it would be easy to do with this.
>
>Lemme know if y'all want to use it; I'll do a little cleanup and
>send it along. It's being used at yahoo by a large developer base,
>I'm confident that it's been well debugged by now.
I haven't seen anyone reply to this, but I would say that this is
very interesting and I'd welcome a patch or even a patched CVS.
cgf
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: overseers@sources.redhat.com
Subject: Re: Controlling cvs commit access
Date: Mon, 16 Oct 2000 16:45:00 -0000 [thread overview]
Message-ID: <20001016194459.B3344@cygnus.com> (raw)
Message-ID: <20001016164500.P1DZ_PmDmDIbxaE_btWhvXAwFtR0R4beu_v2CmQ3Mj0@z> (raw)
In-Reply-To: <20001014002746.A5942@shell17.ba.best.com>
On Sat, Oct 14, 2000 at 12:27:46AM -0700, Jason Molenda wrote:
>We have a large engineering organization at Yahoo with a wider
>variety of cvs uses than I'd seen before. I needed some fine-grained
>way of controlling access to parts of the repository, so I wrote
>a nice little access control list script. It lets you express
>things like
>
> User FOO may only check in changes in directory BAR
>
> Only users FOO, BAR, and BAZ may check in changes in directory BOO
>
> User MOO may not check in any changes to BOO
>
>And all the other variants I could think of as being useful. There
>is a simpler access control script included in the cvs contrib dir
>(cvs_acls.pl), but it sacrifices the expressiveness that my script
>has for much greater simplicity of implementation.
>
>I don't know if this thing would be useful to anyone outside Yahoo,
>but if, for instance, there was ever a hope of merging
>gcc/gdb/binutils/newlib/etc and people were concerned about
>controlling commit policy, it would be easy to do with this.
>
>Lemme know if y'all want to use it; I'll do a little cleanup and
>send it along. It's being used at yahoo by a large developer base,
>I'm confident that it's been well debugged by now.
I haven't seen anyone reply to this, but I would say that this is
very interesting and I'd welcome a patch or even a patched CVS.
cgf
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jason Molenda
2000-10-14 0:28 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor [this message]
2000-10-16 16:45 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-10-16 23:20 ` Jason Molenda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001016194459.B3344@cygnus.com \
--to=cgf@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).