From owner-freebsd-current  Wed Feb 14 09:42:17 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA02522
          for current-outgoing; Wed, 14 Feb 1996 09:42:17 -0800 (PST)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA02516
          for <freebsd-current@FreeBSD.ORG>; Wed, 14 Feb 1996 09:42:14 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.3/8.7.3) with SMTP id JAA00424; Wed, 14 Feb 1996 09:41:25 -0800 (PST)
Message-Id: <199602141741.JAA00424@precipice.shockwave.com>
X-Mailer: exmh version 1.6.5 12/11/95
To: Gary Clark II <gclarkii@freefall.freebsd.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: sup2....:( 
In-reply-to: Your message of "Sun, 11 Feb 1996 14:55:30 PST."
             <199602112255.OAA04679@freefall.freebsd.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Feb 1996 09:41:24 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

Exactly which release were you trying to get, and at what time, and from
what machine (what was your machine)?

I will check the logs.  Clearly, sup/sup locking sucks.  You're not the
first person who has experienced this.

It's my BELIEF that this is happening with -cvs only, and not the standard
source repositories, and it happens due to you doing a sup while I'm doing
a supscan?