X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B9AD.0C15CD49@onstor-exch02.onstor.net>; Thu, 28 Jun 2007 09:52:08 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B9AD.0C15CD49"
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D388@onstor-exch02.onstor.net> <20070628104956.6b67209a@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: cougar builds
Date: Thu, 28 Jun 2007 09:50:13 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D38C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: cougar builds
Thread-Index: Ace5rL1fMqw+rSDNR8eOR4zGCPnMFQAAAn62
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Jeff Miller" <jeff.miller@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B9AD.0C15CD49
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Andy says:

If this does not work, then we need to fix it, because whatever you
were doing before cougar should work with the same expected results.
What I didn't hear is whether or not this worked.

KLR> Thanks Andy. The build did indeed create the cheetah and bobcat =
kernels as expected, I was just checking to see if there is any bits of =
wisdom I needed...sounds like you guys have the backwards =
compatibility-thing down though.

------_=_NextPart_001_01C7B9AD.0C15CD49
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: cougar builds</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Andy says:<BR>
<BR>
If this does not work, then we need to fix it, because whatever you<BR>
were doing before cougar should work with the same expected results.<BR>
What I didn't hear is whether or not this worked.<BR>
<BR>
KLR&gt; Thanks Andy. The build did indeed create the cheetah and bobcat =
kernels as expected, I was just checking to see if there is any bits of =
wisdom I needed...sounds like you guys have the backwards =
compatibility-thing down though.<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B9AD.0C15CD49--
