From owner-freebsd-current  Wed Sep  4 07:35:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA14129
          for current-outgoing; Wed, 4 Sep 1996 07:35:14 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA14123;
          Wed, 4 Sep 1996 07:35:11 -0700 (PDT)
Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id IAA02549; Wed, 4 Sep 1996 08:35:09 -0600 (MDT)
Message-Id: <199609041435.IAA02549@rover.village.org>
To: "Julian H. Stacey" <jhs@FreeBSD.org>
Subject: Re: Latest Current build failure 
Cc: current@FreeBSD.org
In-reply-to: Your message of Wed, 04 Sep 1996 10:54:10 +0200
Date: Wed, 04 Sep 1996 08:35:08 -0600
From: Warner Losh <imp@village.org>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

: We've had developers who produced useful code but were doomed to bad coms
: links.  CTM is asynchronous to net disturbances, so ideal for those with 
: poor net access,  whereas cvsup requires a net in good condition.

And CTM happens async to my desires.  If I go out of town for a week,
it will happily (and correctly to my way of thinking) keep updating
the whole time I'm gone.  I don't have to suck my link down for 6hr
and pray a lot if that is the week that gcc 2.8, perl 6 and tcl 12.3
were committed...  I have plenty of mail spool space :-)

Warner