From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18275 invoked from network); 3 May 2000 09:58:26 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 May 2000 09:58:26 -0000 Received: (qmail 14332 invoked by alias); 3 May 2000 09:58:05 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11098 Received: (qmail 14309 invoked from network); 3 May 2000 09:58:04 -0000 Date: Wed, 3 May 2000 10:57:43 +0100 From: Adam Spiers To: zsh-workers@sunsite.auc.dk Subject: Re: Completion system directories Message-ID: <20000503105743.B14353@thelonious.new.ox.ac.uk> Reply-To: Adam Spiers Mail-Followup-To: zsh-workers@sunsite.auc.dk References: <200005030914.LAA24343@beta.informatik.hu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005030914.LAA24343@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Wed, May 03, 2000 at 11:14:42AM +0200 X-Home-Page: http://www.new.ox.ac.uk/~adam/ X-OS: RedHat Linux Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote: > And finally: what is the easiest way to make these changes in the CVS > repository? Is there really no simpler way than using `cvs add' and > `cvs remove'? If not: urgh. Renaming/moving files around is one of CVS' weaknesses. If we had direct access to the CVS repository we could just copy the RCS files directly, and that would preserve history. (See the FAQ for details of this procedure.) But we don't. So I guess we can either ask the sourceforge guys nicely, or obtain a tarball of the whole repository, and declare the tree closed for a bit while someone messes around with the tarball, and resubmits it for upload. > And that with the `cvs commit aborted: broken pipe' I get at every > second commit-attempt :-( Hmm, no excuse for that. You should submit a bug to sourceforge.