[M3devel] Checkins
Dragiša Durić
dragisha at m3w.org
Mon Mar 24 19:14:44 CET 2008
I would use cvs .... status 2>/dev/null to know what was changed so I
can plan next steps when updating. Usually I do cvs ... diff also. This
way I know what and how was changed before I commit anything.
Works well... Most of time :)
dd
On Mon, 2008-03-24 at 16:37 +0000, 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
>
>
>
>
>
--
Dragiša Durić <dragisha at m3w.org>
More information about the M3devel
mailing list