<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:ns7 =
"urn:schemas-microsoft-com:" xmlns:ns6 =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:ns5 =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ns4 =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ns3 =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:ns2 =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:ns1 =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" XMLNS:D = "DAV:" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:z = "#RowsetSchema" xmlns:rs
= "urn:schemas-microsoft-com:rowset" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:v =
"urn:schemas-microsoft-com:vml"><HEAD><TITLE>RE: [ofw] WDK build environment migration thoughts</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE>@font-face {
font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
A:link {
mso-style-priority: 99
}
SPAN.MSOHYPERLINK {
mso-style-priority: 99
}
A:visited {
mso-style-priority: 99
}
SPAN.MSOHYPERLINKFOLLOWED {
mso-style-priority: 99
}
P {
mso-style-priority: 99
}
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: Calibri; mso-style-type: personal
}
SPAN.EmailStyle19 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=730490219-30042008><FONT face=Arial color=#0000ff size=2>Once
we are sure that the new compiler works well, we should be able to abandon the
DDK build.</FONT></SPAN></DIV>
<DIV><SPAN class=730490219-30042008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=730490219-30042008><FONT face=Arial color=#0000ff
size=2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=730490219-30042008><FONT face=Arial color=#0000ff
size=2>Tzachi</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <B>On Behalf Of </B>Smith,
Stan<BR><B>Sent:</B> Wednesday, April 30, 2008 9:09 PM<BR><B>To:</B> Hefty,
Sean; Fab Tillier; Alex Naslednikov; Ishai Rabinovitz<BR><B>Cc:</B>
ofw@lists.openfabrics.org<BR><B>Subject:</B> RE: [ofw] WDK build environment
migration thoughts<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Hefty, Sean <BR><B>Sent:</B> Wednesday,
April 30, 2008 10:41 AM<BR><B>To:</B> 'Fab Tillier'; Alex Naslednikov; Smith,
Stan; Ishai Rabinovitz<BR><B>Cc:</B>
ofw@lists.openfabrics.org<BR><B>Subject:</B> RE: [ofw] WDK build environment
migration thoughts<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal><FONT face=Calibri color=#1f497d size=2><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: Calibri">Once we confirm
that building in the WDK works, is there any reason to keep supporting the
DDK? I would expect support for the DDK should only be required while
some components don’t build under the WDK.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Calibri color=navy size=2><SPAN
style="FONT-SIZE: 11pt; COLOR: navy; FONT-FAMILY: Calibri"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I say absolutely not.
Supporting the DDK means another at least another dozen builds that must all
be tested.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p><SPAN
class=891050518-30042008><FONT
color=#0000ff></FONT></SPAN></o:p></SPAN></FONT> </P>
<P class=MsoNormal><FONT size=+0><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p><SPAN
class=891050518-30042008><FONT color=#ff00ff>WDK is the 'supported' MS path
- cut the past loose, move forward.
<stan></FONT></SPAN></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p><SPAN
class=891050518-30042008></SPAN> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Calibri color=#1f497d size=2><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: Calibri">It sounds like
the __ptr64 patch failed to meet its objective if 32/64 support is
broken. Just deleting the __ptr64 attribute would have accomplished the
same end result and been ‘cleaner’.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Calibri color=navy size=2><SPAN
style="FONT-SIZE: 11pt; COLOR: navy; FONT-FAMILY: Calibri"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I
agree.<FONT color=#0000ff><SPAN
class=891050518-30042008> </SPAN></FONT></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><FONT
color=#0000ff><SPAN
class=891050518-30042008> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Calibri color=#1f497d size=2><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: Calibri">Also, in the
future please make patches more digestible – there’s no reason ConnectX bug
fixes should have been part of this – they should have been a separate check
in. Having so many changes intermingled, while easier for you to
publish, makes it *<B><SPAN style="FONT-WEIGHT: bold">much</SPAN></B>* harder
to digest. Likewise, the __ptr64 change should have been done
independently of the WDK changes (especially since it introduced a
regression). Your patch touched 3500+ lines of
code.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Just because SVN completely sucks
for patch management doesn’t mean that we need to make patch blob check-ins
standard practice. We really need to look at alternative tools for
Windows that make this easier for developers. Wasn’t Mellanox testing
git internally? What about bitkeeper, is that any
better?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">-
Sean<o:p></o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>