On Fri, Jul 08, 2005 at 11:06:49AM -0600, dann frazier wrote: > On Fri, 2005-07-08 at 11:59 +0900, Horms wrote: > > On the grounds that a) it fixes a security bug and b) it doesn't appear > > to change the ABI, yes, please go for it. > > kernel/sarge-security/kernel/source currently has "testing-security" > instead of UNRELEASED in the changelog in svn - should I put these > patches in 2.6.8-15sarge1, or should I start a sarge2? > > I'll add them to trunk in the meantime.
2.6.8-15sarge1 was never released, although it was packaged up and intended for release, instead 2.6.8-16 snuck in. I think the best place to put pached now is in the main svn directory, as 2.6.8-17. I have already started this. The security update should probably be called 2.6.8-16sarge1, but unless Frank has other ideas, I think that should basically be a paired down package based on whatever we have for 2.6.8-17 at the time. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
