|
From: Andreas R. <And...@gm...> - 2002-05-21 20:48:10
|
Ian, I think this would be great. My major concern is mostly making errors so I wouldn't even require this to be "secure" in any way. What it should do is to make it harder to do stupid mistakes and for that it seems perfectly applicable. Cheers, - Andreas > -----Original Message----- > From: squ...@li... > [mailto:squ...@li...] On Behalf > Of Ian Piumarta > Sent: Tuesday, May 21, 2002 4:44 PM > To: Rob Withers > Cc: squ...@li... > Subject: RE: [Squeak-VMdev] RE: Pending 3.2 and VM sources @ > sourceforge > > > On Mon, 13 May 2002, Rob Withers wrote: > > > > Do we know that we can restrict access to the main trunk to the > > maintainers, then issue expanded rights to select > individuals to their > > branches? > > You can do it with a trivial commitinfo script to filter the usernames > that are allowed to commit to a particular area. (The script > is called on > every commit with env vars and arguments telling who, what, > where, etc. > If the script exits with nonzero then the commit is aborted. > A few lines > of case/sed/test/etc. does the trick.) > > Of course, for this to be in any way secure, SF must only > allow admins to > meddle with the contents of CVSROOT/commitinfo. > > Ciao, > Ian > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Squeak-VMdev mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squeak-vmdev > |