Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 58482 invoked by uid 500); 4 Aug 2002 13:34:33 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 58473 invoked from network); 4 Aug 2002 13:34:32 -0000 Message-ID: <3D4D2D6C.1090207@apache.org> Date: Sun, 04 Aug 2002 09:34:36 -0400 From: Sam Ruby User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: axis-dev@xml.apache.org Subject: Re: CVS locking problems? References: X-Enigmail-Version: 0.62.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Tom Jordahl wrote: > Huh, took build.xml out of my commit and did it separately and everything worked fine. > > Grumble, grumble, crappy version control, mumble... Never seen anything like that before on any cvs project. >>ls -ld /home/cvs > > drwxrwxr-x 158 root cvsadmin 4096 Jul 21 14:01 /home/cvs > >>groups > > tomj apcvs xml > > Is there something wrong here? Where do problems like this get reported? You should be able to write to /home/cvs/xml-axis, but only read /home/cvs. infrastructure@apache.org is a good place to post such questions. - Sam Ruby