[M3devel] Checkins

[Tony Hosking]

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.

On Mar 24, 2008, at 12:37 PM, Jay wrote:

> Tony, The problem was I forgot to add a file, right?
> 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.
> After commiting, I updated another machine, noticed the missing  
> file, added it.
>
> I thought other than the forgotten file, the changes were coherent,  
> at least for non-NT386GNU.
>
>  - Jay
> From: hosking at cs.purdue.edu
> To: m3devel at elegosoft.com
> Date: Mon, 24 Mar 2008 10:36:56 -0400
> CC: jkrell at elego.de
> Subject: [M3devel] Checkins
>
> 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.
>
> If we use the tools properly, then everyone can play nicely together.
>
> Antony Hosking | Associate Professor | Computer Science | Purdue  
> University
> 305 N. University Street | West Lafayette | IN 47907 | USA
> Office +1 765 494 6001 | Mobile +1 765 427 5484
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080324/0c062ec4/attachment-0002.html>