Re: spinlocks

I guess so...
I don't really mind them concentrating on their own efforts here. This
is a project they are working on for school. If they don't want to at
least let people view their code I find that weird but not rude.
I assume they will release the code after they are finished....


On Mon, 2002-12-09 at 23:12, Mark Beihoffer wrote:
> ok, true enough, I didn't know they were blocking access to CVS reads.
> They're not sharing the source?
> 
> 
> ----- Original Message -----
> From: "Will Ellis-Adams" <[email protected]>
> To: "Mark Beihoffer" <[email protected]>
> Sent: Monday, January 14, 2002 11:49 PM
> Subject: Re: spinlocks
> 
> 
> > I just mean to get the actual code not to give write access. I would think
> > changes should be submitted for them to look over....
> > Or do you mean that even without write access someone might hack into it?
> >
> > ----- Original Message -----
> > From: "Mark Beihoffer" <[email protected]>
> > To: "Will Ellis-Adams" <[email protected]>
> > Sent: Monday, December 09, 2002 10:46 PM
> > Subject: Re: spinlocks
> >
> >
> > > Hmm - who would be auditing the anonymous CVS entries?
> > >
> > > I'm a little paranoid that someone might try to slip a backdoor into the
> > SMP
> > > branch.
> > >
> > > ----- Original Message -----
> > > From: "Will Ellis-Adams" <[email protected]>
> > > To: <[email protected]>
> > > Sent: Monday, January 14, 2002 11:30 PM
> > > Subject: spinlocks
> > >
> > >
> > > > Looks like spinlocks.org got Slashdoted.
> > > > Maybe this will stir up some more SMP Motivation ;)
> > > > Are you planning on giving anoncvs access to the code
> > > > anytime soon? (spinlocks) I know cvs access was internal-only.
> > > > You may find some help optimizing it that way. Also
> > > > finding bugs etc...
> > > >                                 -Will