Sorry! Forget what I said. I just got a freeze with the latest git
drivers, I guess this is still a problem. It just took much longer to
appear than before. I guess this bug is still open. I've been
regression-testing it using git bisect, and I think I found the commit
that broke it, but in light of this unexpected freeze I think I need
to keep testing the revision I think is good to make sure.

2008/5/18 Debian Bug Tracking System <[EMAIL PROTECTED]>:
>
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian X Strike Force <[EMAIL PROTECTED]>
>
> If you wish to submit further information on this problem, please
> send it to [EMAIL PROTECTED], as before.
>
> Please do not send mail to [EMAIL PROTECTED] unless you wish
> to report a problem with the Bug-tracking system.
>
>
> --
> 479870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479870
> Debian Bug Tracking System
> Contact [EMAIL PROTECTED] with problems
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to