From owner-freebsd-ports  Sat Dec 28 16:43:28 1996
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id QAA05653
          for ports-outgoing; Sat, 28 Dec 1996 16:43:28 -0800 (PST)
Received: from dfw-ix11.ix.netcom.com (dfw-ix11.ix.netcom.com [206.214.98.11])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA05641
          for <freebsd-ports@freebsd.org>; Sat, 28 Dec 1996 16:43:24 -0800 (PST)
Received: from baloon.mimi.com (sjx-ca56-03.ix.netcom.com [205.186.122.67]) by dfw-ix11.ix.netcom.com (8.6.13/8.6.12) with ESMTP id QAA00285; Sat, 28 Dec 1996 16:42:50 -0800
Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id QAA16301; Sat, 28 Dec 1996 16:42:47 -0800 (PST)
Date: Sat, 28 Dec 1996 16:42:47 -0800 (PST)
Message-Id: <199612290042.QAA16301@baloon.mimi.com>
To: deobrien@ucdavis.edu
CC: freebsd-ports@freebsd.org
In-reply-to: <Mutt.19961227021904.obrien@dragon.nuxi.com>
Subject: Re: bsd.port.mk on freefall
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Are we really supose to be able to do a cvs co/update on thud?  I've
 * asked Peter several times in email this question and have yet to get an
 * answer.  For some ports (like mutt) it works, on others (like elm) I get
 * lock file errors.

Yes, it is supposed to work.  I never had any problems there (although 
I don't use thud much these days).

I just noticed you were not in group ncvs, maybe that was why.  I
added you, so try again.

Satoshi