Alex Ionescu wrote:
it's extremly hard to find
a broken revision, and requires going through each one by hand (just
like the MmInit1 changes this week, for example).
Just to note, the only reason the MmInit1 changes wern't quick to find was
that buildbot was down for some obscure reason.
If buildbot had been running (as it normally is), we would have imediatley
spotted that 2nd stage was broken via the system regression tool, which is
now incorporated into buildbot.
As it happens, the first time our sysreg tool was required, buildbot was
down so we couldn't make use of it.
Sods law .... or maybe we could blame Christoph ;)
Ged.
This message contains confidential information and is intended only for the individual
named. If you are not the named addressee you should not disseminate, distribute or copy
this e-mail. Please notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does
not accept liability for any errors or omissions in the contents of this message, which
arise as a result of e-mail transmission. If verification is required please request a
hard-copy version.
Amteus Secure Communications Ltd
57 Cardigan Lane,
Leeds,
LS4 2LE
t: +44 (0) 870 8368770
f: +44 (0) 870 8368701
Registered in England No 4760795
http://www.amteus.com