-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 sean finney wrote: > okay, thanks for helping with the clarifications. if it was a regression in > the security update then it's possible that an update could also go through > via another security update. i'll go ahead and merge it into the etch branch > > and then you'll get it from either the stable point release or the next > security release, whichever comes first.
Hey Sean, that would be fantastic. Thanks a lot for being so responsive on this bug :) Penny - -- Penny Leach | [EMAIL PROTECTED] | +64 21 736 695 Catalyst IT | http://catalyst.net.nz | +64 4 803 2218 GPG 8347 00FC B5BF 6CC0 0FC9 AB90 1875 120A A30E C22B -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVgbfGHUSCqMOwisRAh8BAKDIE9vUIQ4TuNgZpBZBRa/I91N5xACggMue AiX93ZBPk1osbjKDdQTGdlM= =Q8pq -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
