<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>hm, cvs release, didn't know about that.<BR>
I thought I had been much slower actually.<BR>
I added a file first, to better show history, then one well tested, on one platform, thought to be coherent checkin, then updated my Mac and found the missing file, fixed it, etc. There was also a missing file for NT386GNU that nobody would notice. I also set up my testing to build the more-Posix path on NT386GNU to be sure it built and ran. I am not much into the habit of testing on more than one machine/platform before submitting, though sometimes, and actually NT386GNU makes that easier -- two platforms on one machine. I am more in the habit of testing other machines right after commit.<BR>
I haven't found a convenient way to move changes..cvs diff into a file, copy that, and patch? Or maybe share out the tree over the network and build in one tree directly? I should probably try that..<BR>
<BR>
And I can't checkin from the top as I have other definitely unrelated unfinished un-affecting changes, true that sets a trap for myself.<BR>
<BR>
Without the commit mail, what do you run to see recent commits?<BR>
cvs filelog likes to default to showing the full history.<BR>
I'd like to say, just show the last 10 commits, or the last 20 commits..<BR>
I'm operating relatively blindly wrt cvs skills I'm afraid.<BR>
<BR>
And you manually check the tinderbox pages? They don't send mail?<BR>
<BR>
I do run cvs diff but I have a bunch of junk..gotta clean it up..<BR>
<BR>
? bin<BR>? caltech-parser/parserlib/.parsertop<BR>? caltech-parser/parserlib/html/SeekRd.html<BR>? caltech-parser/parserlib/html/calc.html<BR>? caltech-parser/parserlib/html/index.html<BR>? caltech-parser/parserlib/html/kext.html<BR>? caltech-parser/parserlib/html/klex.html<BR>? caltech-parser/parserlib/html/ktok.html<BR>? caltech-parser/parserlib/html/kyacc.html<BR>? caltech-parser/parserlib/html/lr.html<BR>? caltech-parser/parserlib/html/m3build.html<BR>? caltech-parser/parserlib/html/macroizations<BR>? m3-db/smalldb/src/mine<BR>? m3-db/smalldb/src/orig<BR>? <FONT face="">m3-libs</FONT>/arithmetic/NT386<BR>? <FONT face="">m3-libs</FONT>/arithmetic/NT386GNU<BR>? <FONT face="">m3-libs</FONT>/commandrw/NT386<BR>? <FONT face="">m3-libs</FONT>/commandrw/SOLgnu<BR>? <FONT face="">m3-libs</FONT>/deepcopy/NT386<BR>? <FONT face="">m3-libs</FONT>/libm3/src/os/NT386GNU<BR>? <FONT face="">m3-libs</FONT>/libm3/src/os/POSIX/ProcessCygwin.<FONT face="">m3</FONT><BR><BR><BR> - Jay<BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
CC: m3devel@elegosoft.com; jkrell@elego.de<BR>From: hosking@cs.purdue.edu<BR>To: jayk123@hotmail.com<BR>Subject: Re: [M3devel] Checkins<BR>Date: Mon, 24 Mar 2008 12:43:31 -0400<BR><BR>
<DIV>I didn't take the time to look to closely at what caused the failure, but I did notice a smear of checkins spread over time. Better to roll it all into one checkin. I usually do a cvs release to see if there are files (marked by ?) that I forgot to add, and add them, before doing the big checkin as one top-level command.</DIV>
<DIV></DIV><BR>
<DIV>On Mar 24, 2008, at 12:37 PM, Jay wrote:<BR class=EC_Apple-interchange-newline>
<BLOCKQUOTE><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<DIV class=EC_hmmessage style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Tony, The problem was I forgot to add a file, right?<BR>That's something the tools are setup to make you fail at as I understand. Right? I have to remember to cvs add whenever I create a file. Building works either way.<BR>After commiting, I updated another machine, noticed the missing file, added it.<BR> <BR>I thought other than the forgotten file, the changes were coherent, at least for non-NT386GNU.<BR> <BR> - Jay<BR>
<BLOCKQUOTE>
<HR id=EC_EC_stopSpelling>
From:<SPAN class=EC_Apple-converted-space> </SPAN><A href="mailto:hosking@cs.purdue.edu">hosking@cs.purdue.edu</A><BR>To:<SPAN class=EC_Apple-converted-space> </SPAN><A href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</A><BR>Date: Mon, 24 Mar 2008 10:36:56 -0400<BR>CC:<SPAN class=EC_Apple-converted-space> </SPAN><A href="mailto:jkrell@elego.de">jkrell@elego.de</A><BR>Subject: [M3devel] Checkins<BR><BR>
<DIV>It seems that the reason things failed is because a checkin of multiple related changes was not done as a single atomic commit. This meant that partial checkout of inconsistent code occurred while bits and pieces of a coherent set of changes were being singly checked in. Please try to bulk checkin related changes so as to avoid these sorts of inconsistencies. cvs does a great job of bundling an entire set of changes as one commit. It also has the nice side-effect of not bombarding folks with zillions of commit e-mails -- instead the bundled commit comes in one message.</DIV>
<DIV><BR></DIV>
<DIV>If we use the tools properly, then everyone can play nicely together.</DIV><BR>
<DIV><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<DIV style="WORD-WRAP: break-word"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<DIV><FONT class=EC_EC_Apple-style-span face="" color=#0000ff><FONT class=EC_EC_Apple-style-span face="Gill Sans"><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'">Antony Hosking</SPAN></SPAN></FONT></FONT><FONT class=EC_EC_Apple-style-span face="Gill Sans"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_Apple-converted-space> </SPAN>|<SPAN class=EC_Apple-converted-space> </SPAN></SPAN></SPAN><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'">Associate Professor</SPAN></SPAN><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: 'Gill Sans'"> | Computer Science | Purdue University</SPAN></SPAN></FONT></DIV>
<DIV><FONT class=EC_EC_Apple-style-span face=GillSans-Light><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: GillSans-Light">305 N. University Street | West Lafayette | IN 47907 | USA</SPAN></FONT></DIV>
<DIV><FONT class=EC_EC_Apple-style-span face="Gill Sans" color=#0000ff><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'">Office</SPAN></SPAN></FONT><FONT class=EC_EC_Apple-style-span face=GillSans-Light><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"> +1 765 494 6001 |<SPAN class=EC_Apple-converted-space> </SPAN></SPAN></SPAN></FONT><FONT class=EC_EC_Apple-style-span face="Gill Sans" color=#0000ff><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'"><SPAN class=EC_EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: 'Gill Sans'">Mobile</SPAN></SPAN></FONT><FONT class=EC_EC_Apple-style-span face=GillSans-Light><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"><SPAN class=EC_EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"><SPAN class=EC_Apple-converted-space> </SPAN>+1 765 427 5484</SPAN></SPAN></FONT></DIV>
<DIV><FONT class=EC_EC_Apple-style-span face=GillSans-Light><BR class=EC_EC_khtml-block-placeholder></FONT></DIV></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN><BR class=EC_EC_Apple-interchange-newline></SPAN></DIV></SPAN></DIV><BR></BLOCKQUOTE></DIV></SPAN><BR class=EC_Apple-interchange-newline></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></body>
</html>