On Fri, Oct 07, 2005 at 10:42:26AM -0600, dann frazier wrote:
> On Fri, 2005-10-07 at 09:49 -0400, micah wrote:
> > Hey,
> >
> > Horms wrote:
> > > On Fri, Oct 07, 2005 at 12:21:38AM -0600, dann frazier wrote:
> > >
> > >>In order to hopefully help kickstart the security update process, I've
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dann frazier wrote:
>
> I'm up for helping, but might not have much time till next week. I'm
> travelling to the east coast for work, but should have net there. I see
> dilinger was setting you up w/ commit access - do you wanna use a file
> ther
On Fri, 2005-10-07 at 09:49 -0400, micah wrote:
> Hey,
>
> Horms wrote:
> > On Fri, Oct 07, 2005 at 12:21:38AM -0600, dann frazier wrote:
> >
> >>In order to hopefully help kickstart the security update process, I've
> >>drafted some DSA text for our sarge/2.6.8 kernels (attached). Thanks to
> >
Hey,
Horms wrote:
> On Fri, Oct 07, 2005 at 12:21:38AM -0600, dann frazier wrote:
>
>>In order to hopefully help kickstart the security update process, I've
>>drafted some DSA text for our sarge/2.6.8 kernels (attached). Thanks to
>>Micah, we have CAN IDs assigned for a number of things we just
On Fri, Oct 07, 2005 at 12:21:38AM -0600, dann frazier wrote:
> In order to hopefully help kickstart the security update process, I've
> drafted some DSA text for our sarge/2.6.8 kernels (attached). Thanks to
> Micah, we have CAN IDs assigned for a number of things we just had
> marked as security
In order to hopefully help kickstart the security update process, I've
drafted some DSA text for our sarge/2.6.8 kernels (attached). Thanks to
Micah, we have CAN IDs assigned for a number of things we just had
marked as security. I tried to map all of the patches to CANs, but
these are the ones r
6 matches
Mail list logo
