[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Playing the KDE CVS roulette
From:       Michael =?iso-8859-1?q?H=E4ckel?= <haeckel () kde ! org>
Date:       2001-12-26 14:49:19
[Download RAW message or body]

On Wednesday 26 December 2001 15:29, Bryce Nesbitt wrote:
>
> I don't think I'm the only one.  I often see messages on the list about
> broken compiles. I'm not surprised it does not work, actually.  No matter
> what time you CVS update you're going to catch SOMEONE in the middle of a
> checkin.  This may or may not produce a compile error.  We're all always
> testing something that's not quite fully checked in.
>
> The harder the developers work (and they do work hard) to make fixes and
> checkins, the worse the problem gets.  My question is is there a procedural
> or technical solution to avoiding catching checkins in the middle?  It's
> not a matter of dilligence on the part of the developers, it's a technical
> matter.

This is not quite possible. CVS handles this nicely.
If a checkin is in progress, you get a nice message that CVS is waiting for 
the lock in that directory. If the checking is finished your update 
continues.

Regards,
Michael Häckel
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]