X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C57C.B796B15F@onstor-exch02.onstor.net>; Fri, 13 Jul 2007 10:36:25 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C57C.B796B15F"
Content-class: urn:content-classes:message
Subject: RE: Zonda Submittal 3 Ready for AT
Date: Fri, 13 Jul 2007 10:36:24 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0485CB1D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03E56A61@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Zonda Submittal 3 Ready for AT
Thread-Index: AcfE582mBOLvYwBhQNGf/1qQUX6bCQAKeIyVABSc0NAABMqcMAAAMyRKAAD1vxA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E02EB2F5E@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03E56A61@onstor-exch02.onstor.net>
From: "Erik Palomba" <erik.palomba@onstor.com>
To: "Paul Hammer" <paul.hammer@onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Durairaj Muthusamy" <durairaj.muthusamy@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7C57C.B796B15F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would strongly prefer to only see listed what will affect Zonda. We
can then determine AT and what have you based on that. From my
perspective, I would have no way of knowing what should be changed and
what should not be changed for Zonda. =20

=20

I think any processes that are done to give us the Zonda submittals are
out of my hands.=20

=20

=20

________________________________

From: Paul Hammer=20
Sent: Friday, July 13, 2007 11:03 AM
To: Ken Renshaw; Brian DeForest; Sandrine Boulanger; Erik Palomba;
Durairaj Muthusamy
Cc: Andy Sharp; Larry Scheer
Subject: RE: Zonda Submittal 3 Ready for AT

=20

I don't think it makes sense for the Zonda team, should filter out the
noise so that the team can focus on the Zonda specific changes.

=20

________________________________

From: Ken Renshaw
Sent: Fri 7/13/2007 10:57 AM
To: Brian DeForest; Paul Hammer; Sandrine Boulanger; Erik Palomba;
Durairaj Muthusamy
Cc: Andy Sharp; Larry Scheer
Subject: Re: Zonda Submittal 3 Ready for AT

I agree, I just didn't think it made a lot of sense in the singular case
of this build to list all the cougar changes up to this point.

From now on I'll include all changes done in the branch, as this makes
sense.

Thanks,

-Ken



-----Original Message-----
From: Brian DeForest
To: Paul Hammer; Ken Renshaw; Sandrine Boulanger; Erik Palomba; Durairaj
Muthusamy
CC: Andy Sharp; Larry Scheer
Sent: Fri Jul 13 10:29:45 2007
Subject: RE: Zonda Submittal 3 Ready for AT

Disagree.  The only way to tell if a Cougar-specific changelist WILL NOT
be included in the Zonda build is to check every file in every
changelist and verify that only Cougar-specific files have changes.
Stated another way, if ANY common files are changed, the changelist will
effect Zonda.



So going forward, since we have one branch, unless you plan to review
every file changed in every changelist, AND you know which files are
Cougar-specific, I would suggest simply listing every changelist since
the previous submittal, and leave it to the engineers to determine if
the changelist is relevant for Zonda or not.=20



I think it's better to have too many changelists listed in the submittal
notes than to selectively list some (which is error prone).



________________________________

From: Paul Hammer
Sent: Thursday, July 12, 2007 10:50 PM
To: Ken Renshaw; Sandrine Boulanger; Erik Palomba; Brian DeForest;
Durairaj Muthusamy
Cc: Andy Sharp; Larry Scheer
Subject: RE: Zonda Submittal 3 Ready for AT



Great Ken. Lets start the AT Durai, thanks. Looking forward to seeing a
positive result tomorrow of this in the status report.



Assume that we will not list any branch changes/checkins that are done
in Cougar to the Zonda team for the remainder of the Zonda submittal
(project contest only)? Makes sense from the Zonda perspective.  Do we
have submittal notes for this thing?



We are off!



-Paul





________________________________

From: Ken Renshaw
Sent: Thu 7/12/2007 10:46 PM
To: Sandrine Boulanger; Erik Palomba; Brian DeForest; Durairaj Muthusamy
Cc: Ken Renshaw; Paul Hammer; Andy Sharp; Larry Scheer
Subject: Zonda Submittal 3 Ready for AT

Here is the first submittal of Zonda after melding the old project
branch into the Cougar branch.

The new BSD version to point your /usr/openbsd.new symlinks to has been
built and is posted here:

/n/Build-Trees/BSD/openbsd-latest-310

Which in turn points to:

/n/Build-Trees/BSD/openbsd-071207-310

Just use the first one and you'll be fine as I rev OS versions. Diehards
who build their own please ignore.

Changes since Zonda submittal 2:

Change 24543 on 2007/07/12 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
18335-NCM: it would'
Change 24542 on 2007/07/11 by jobia@jobi:jobi '   Minor changes:
Some cove'
Change 24541 on 2007/07/11 by henryl@henryl-linux '   Additional fix for
sprintf t'
Change 24540 on 2007/07/11 by mikel@mikel-work '   Fun with Coverity
Part 3 - E'
Change 24539 on 2007/07/11 by henryl@henryl-linux '   Change sprintf to
snprintf s'
Change 24535 on 2007/07/11 by edk@edk-zonda 'Changes for TED 19444.  Do
not '
Change 24533 on 2007/07/11 by edk@edk-zonda 'Changes for defect 19716.
Sets'
Change 24532 on 2007/07/11 by jobia@jobi:jobi '   Fix one of the new
asserts f'
Change 24531 on 2007/07/11 by henryl@henryl-linux '   Inject error to
security des'
Change 24529 on 2007/07/11 by jobia@jobi:jobi '   Block information
tracked in'
Change 24528 on 2007/07/11 by jobia@jobi:jobi '   EEK allocates missing
securi'
Change 24524 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
18705-NCM: we shoul'
Change 24523 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'
Change 24522 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug
ID:TED00019767 (OLH'
Change 24521 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'
Change 24520 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug
ID:TED00019767 (OLH'
Change 24519 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Big ID:
TED00019767 (OL'
Change 24518 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'
Change 24516 on 2007/07/10 by henryl@henryl-linux '   Fixed TED#19769.
Fixed the v'
Change 24510 on 2007/07/10 by jobia@jobi:jobi '   Initialize newly
allocated i'
Change 24509 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug 19170-
NCM : Improp'
Change 24508 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
18706-NCM: The note'
Change 24507 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
TED00017229-NCM add'
Change 24505 on 2007/07/09 by henryl@henryl-linux '   Remove several
areas with no'
Change 24492 on 2007/07/09 by jobia@jobi:jobi 'Fix a case where inode
was inco'
Change 24488 on 2007/07/09 by jobia@jobi:jobi '   COW should not blindly
skipp'
Change 24485 on 2007/07/08 by jobia@jobi:jobi '   Remove checks for NULL
inode'
Change 24484 on 2007/07/08 by jobia@jobi:jobi 'EEK should not assert if
inodes'
Change 24483 on 2007/07/08 by jobia@jobi:jobi '   Skip reading refcounts
for o'
Change 24481 on 2007/07/07 by jobia@jobi:jobi2 'Do not convert a flat
emap, if '
Change 24480 on 2007/07/07 by jobia@jobi:jobi2 'Fix a watch dog timeout
in fs_b'
Change 24479 on 2007/07/07 by jobia@jobi:jobi2 '   Do not flush dirty
inodes to'
Change 24464 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'fix for bug
TED00018332-NCM: vs'
Change 24463 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
17249-NCM shouldn't'
Change 24462 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
16091-Message for c'
Change 24461 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
16336-Set Domain di'
Change 24460 on 2007/07/05 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
17211-NCM Autocreat'
Change 24459 on 2007/07/05 by mikel@mikel-work '   Fix opt build problem
due to'
Change 24457 on 2007/07/05 by mikel@mikel-work '   for coverity
discovered bugs'
Change 24441 on 2007/07/03 by mikel@mikel-work '   For defect 19685,
where a st'
Change 24436 on 2007/07/03 by charissaw@charissaw-unix-fb-zonda-work
'TED00019721 - Commented out "Do'
Change 24435 on 2007/07/02 by kenr@build-k2-depot 'DeLorean final bits.
Integratio'

The sum total of Cougar work also resides alongside this codebase now,
but we'll consider it invisible WRT to Zonda for the time being. By and
large it's worked out that way.

EverON images:

Cheetah debug:

ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0DBG-071207.tar.gz

Bobcat debug:

ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BCDBG-071207.tar.gz

Cheetah optimized:

ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0-071207.tar.gz

Bobcat optimized:

ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BC-071207.tar.gz

Source tree:

/n/Build-Trees/R3.1.0.0/R3.1.0.0-071207/nfx-tree

Perforce sync info:

//depot/cougar/...@24557

Thanks,

-Ken
















------_=_NextPart_001_01C7C57C.B796B15F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: Zonda Submittal 3 Ready for AT</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Tahoma;
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>I would strongly prefer to only =
see
listed what will affect Zonda. We can then determine AT and what have =
you based
on that. From my perspective, I would have no way of knowing what should =
be
changed and what should not be changed for Zonda. =
&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'>I think any processes that are =
done to
give us the Zonda submittals are out of my hands. =
</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:black'><o:p>&nbsp;</o:p></span></font></p=
>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Paul =
Hammer <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, July 13, =
2007 11:03
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Ken Renshaw; Brian =
DeForest;
Sandrine Boulanger; Erik Palomba; Durairaj Muthusamy<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Andy Sharp; Larry =
Scheer<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Zonda =
Submittal 3
Ready for AT</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div id=3DidOWAReplyText74270>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>I don't think it makes sense for =
the
Zonda team, should filter out the noise so that the team can focus on =
the Zonda
specific changes.</span></font><o:p></o:p></p>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Ken
Renshaw<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Fri 7/13/2007 10:57 =
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Brian DeForest; Paul =
Hammer;
Sandrine Boulanger; Erik Palomba; Durairaj Muthusamy<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Andy Sharp; Larry =
Scheer<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: Zonda =
Submittal 3
Ready for AT</span></font><o:p></o:p></p>

</div>

<div>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>I agree, I just didn't think it made a lot of =
sense in
the singular case of this build to list all the cougar changes up to =
this point.<br>
<br>
From now on I'll include all changes done in the branch, as this makes =
sense.<br>
<br>
Thanks,<br>
<br>
-Ken<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Brian DeForest<br>
To: Paul Hammer; Ken Renshaw; Sandrine Boulanger; Erik Palomba; Durairaj
Muthusamy<br>
CC: Andy Sharp; Larry Scheer<br>
Sent: Fri Jul 13 10:29:45 2007<br>
Subject: RE: Zonda Submittal 3 Ready for AT<br>
<br>
Disagree.&nbsp; The only way to tell if a Cougar-specific changelist =
WILL NOT
be included in the Zonda build is to check every file in every =
changelist and
verify that only Cougar-specific files have changes.&nbsp; Stated =
another way,
if ANY common files are changed, the changelist will effect Zonda.<br>
<br>
<br>
<br>
So going forward, since we have one branch, unless you plan to review =
every
file changed in every changelist, AND you know which files are =
Cougar-specific,
I would suggest simply listing every changelist since the previous =
submittal,
and leave it to the engineers to determine if the changelist is relevant =
for
Zonda or not.&nbsp;<br>
<br>
<br>
<br>
I think it&#8217;s better to have too many changelists listed in the =
submittal
notes than to selectively list some (which is error prone).<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Paul Hammer<br>
Sent: Thursday, July 12, 2007 10:50 PM<br>
To: Ken Renshaw; Sandrine Boulanger; Erik Palomba; Brian DeForest; =
Durairaj
Muthusamy<br>
Cc: Andy Sharp; Larry Scheer<br>
Subject: RE: Zonda Submittal 3 Ready for AT<br>
<br>
<br>
<br>
Great Ken. Lets start the AT Durai, thanks. Looking forward to seeing a
positive result tomorrow of this in the status report.<br>
<br>
<br>
<br>
Assume that we will not list any branch changes/checkins that are done =
in
Cougar to the Zonda team for the remainder of the Zonda submittal =
(project
contest only)? Makes sense from the Zonda perspective.&nbsp; Do we have
submittal notes for this thing?<br>
<br>
<br>
<br>
We are off!<br>
<br>
<br>
<br>
-Paul<br>
<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Ken Renshaw<br>
Sent: Thu 7/12/2007 10:46 PM<br>
To: Sandrine Boulanger; Erik Palomba; Brian DeForest; Durairaj =
Muthusamy<br>
Cc: Ken Renshaw; Paul Hammer; Andy Sharp; Larry Scheer<br>
Subject: Zonda Submittal 3 Ready for AT<br>
<br>
Here is the first submittal of Zonda after melding the old project =
branch into
the Cougar branch.<br>
<br>
The new BSD version to point your /usr/openbsd.new symlinks to has been =
built
and is posted here:<br>
<br>
/n/Build-Trees/BSD/openbsd-latest-310<br>
<br>
Which in turn points to:<br>
<br>
/n/Build-Trees/BSD/openbsd-071207-310<br>
<br>
Just use the first one and you'll be fine as I rev OS versions. Diehards =
who
build their own please ignore.<br>
<br>
Changes since Zonda submittal 2:<br>
<br>
Change 24543 on 2007/07/12 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
18335-NCM: it
would'<br>
Change 24542 on 2007/07/11 by jobia@jobi:jobi '&nbsp;&nbsp; Minor
changes:&nbsp;&nbsp;&nbsp;&nbsp; Some cove'<br>
Change 24541 on 2007/07/11 by henryl@henryl-linux '&nbsp;&nbsp; =
Additional fix
for sprintf t'<br>
Change 24540 on 2007/07/11 by mikel@mikel-work '&nbsp;&nbsp; Fun with =
Coverity
Part 3 - E'<br>
Change 24539 on 2007/07/11 by henryl@henryl-linux '&nbsp;&nbsp; Change =
sprintf
to snprintf s'<br>
Change 24535 on 2007/07/11 by edk@edk-zonda 'Changes for TED =
19444.&nbsp; Do
not '<br>
Change 24533 on 2007/07/11 by edk@edk-zonda 'Changes for defect =
19716.&nbsp;
Sets'<br>
Change 24532 on 2007/07/11 by jobia@jobi:jobi '&nbsp;&nbsp; Fix one of =
the new
asserts f'<br>
Change 24531 on 2007/07/11 by henryl@henryl-linux '&nbsp;&nbsp; Inject =
error to
security des'<br>
Change 24529 on 2007/07/11 by jobia@jobi:jobi '&nbsp;&nbsp; Block =
information
tracked in'<br>
Change 24528 on 2007/07/11 by jobia@jobi:jobi '&nbsp;&nbsp; EEK =
allocates
missing securi'<br>
Change 24524 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
18705-NCM: we
shoul'<br>
Change 24523 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'<br>
Change 24522 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug
ID:TED00019767 (OLH'<br>
Change 24521 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'<br>
Change 24520 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug
ID:TED00019767 (OLH'<br>
Change 24519 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Big ID:
TED00019767 (OL'<br>
Change 24518 on 2007/07/10 by perforce@NAVANEETHANP-WI 'Fix for Bug ID:
TED00019767 (OL'<br>
Change 24516 on 2007/07/10 by henryl@henryl-linux '&nbsp;&nbsp; Fixed
TED#19769. Fixed the v'<br>
Change 24510 on 2007/07/10 by jobia@jobi:jobi '&nbsp;&nbsp; Initialize =
newly
allocated i'<br>
Change 24509 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug 19170- =
NCM :
Improp'<br>
Change 24508 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
18706-NCM: The
note'<br>
Change 24507 on 2007/07/10 by sahayaj@SAHAYAJ-WINXP 'Fix for bug
TED00017229-NCM add'<br>
Change 24505 on 2007/07/09 by henryl@henryl-linux '&nbsp;&nbsp; Remove =
several
areas with no'<br>
Change 24492 on 2007/07/09 by jobia@jobi:jobi 'Fix a case where inode =
was inco'<br>
Change 24488 on 2007/07/09 by jobia@jobi:jobi '&nbsp;&nbsp; COW should =
not
blindly skipp'<br>
Change 24485 on 2007/07/08 by jobia@jobi:jobi '&nbsp;&nbsp; Remove =
checks for
NULL inode'<br>
Change 24484 on 2007/07/08 by jobia@jobi:jobi 'EEK should not assert if =
inodes'<br>
Change 24483 on 2007/07/08 by jobia@jobi:jobi '&nbsp;&nbsp; Skip reading
refcounts for o'<br>
Change 24481 on 2007/07/07 by jobia@jobi:jobi2 'Do not convert a flat =
emap, if
'<br>
Change 24480 on 2007/07/07 by jobia@jobi:jobi2 'Fix a watch dog timeout =
in
fs_b'<br>
Change 24479 on 2007/07/07 by jobia@jobi:jobi2 '&nbsp;&nbsp; Do not =
flush dirty
inodes to'<br>
Change 24464 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'fix for bug
TED00018332-NCM: vs'<br>
Change 24463 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
17249-NCM
shouldn't'<br>
Change 24462 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
16091-Message
for c'<br>
Change 24461 on 2007/07/06 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
16336-Set
Domain di'<br>
Change 24460 on 2007/07/05 by sahayaj@SAHAYAJ-WINXP 'Fix for bug =
17211-NCM
Autocreat'<br>
Change 24459 on 2007/07/05 by mikel@mikel-work '&nbsp;&nbsp; Fix opt =
build
problem due to'<br>
Change 24457 on 2007/07/05 by mikel@mikel-work '&nbsp;&nbsp; for =
coverity
discovered bugs'<br>
Change 24441 on 2007/07/03 by mikel@mikel-work '&nbsp;&nbsp; For defect =
19685,
where a st'<br>
Change 24436 on 2007/07/03 by charissaw@charissaw-unix-fb-zonda-work
'TED00019721 - Commented out &quot;Do'<br>
Change 24435 on 2007/07/02 by kenr@build-k2-depot 'DeLorean final bits.
Integratio'<br>
<br>
The sum total of Cougar work also resides alongside this codebase now, =
but
we'll consider it invisible WRT to Zonda for the time being. By and =
large it's
worked out that way.<br>
<br>
EverON images:<br>
<br>
Cheetah debug:<br>
<br>
<a =
href=3D"ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0DBG-071207.tar.gz">ft=
p://upgrade@10.2.0.2/home/upgrade/R3.1.0.0DBG-071207.tar.gz</a><br>
<br>
Bobcat debug:<br>
<br>
<a =
href=3D"ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BCDBG-071207.tar.gz">=
ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BCDBG-071207.tar.gz</a><br>
<br>
Cheetah optimized:<br>
<br>
<a =
href=3D"ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0-071207.tar.gz">ftp:/=
/upgrade@10.2.0.2/home/upgrade/R3.1.0.0-071207.tar.gz</a><br>
<br>
Bobcat optimized:<br>
<br>
<a =
href=3D"ftp://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BC-071207.tar.gz">ftp=
://upgrade@10.2.0.2/home/upgrade/R3.1.0.0BC-071207.tar.gz</a><br>
<br>
Source tree:<br>
<br>
/n/Build-Trees/R3.1.0.0/R3.1.0.0-071207/nfx-tree<br>
<br>
Perforce sync info:<br>
<br>
//depot/cougar/...@24557<br>
<br>
Thanks,<br>
<br>
-Ken<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7C57C.B796B15F--
