From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22678 invoked from network); 3 May 2000 16:51:56 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 May 2000 16:51:56 -0000 Received: (qmail 8144 invoked by alias); 3 May 2000 16:51:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11132 Received: (qmail 8071 invoked from network); 3 May 2000 16:51:39 -0000 Date: Wed, 03 May 2000 17:51:12 +0100 From: Peter Stephenson Subject: Re: Completion system directories In-reply-to: "Your message of Wed, 03 May 2000 16:35:45 -0000." <1000503163546.ZM21934@candle.brasslantern.com> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FTZ00LEDTHBNF@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT Bart wrote: > How about this: > > Leave the renaming alone until 4.0. > > When we're ready to do 4.0, rename the entire existing repository to > "zsh-3.1" and create a new repository, with all the files in the right > places and no revision history. I.e., make up the 4.0 tarball and then > "cvs import" it into the fresh repository. This would probably be fine, although I'm not sure we're able to rename the repository as such. We can create a new tree under /cvsroot/zsh rooted on zsh-4.0, and possibly alias it under the name `zsh' (not sure about this if there's a directory zsh, but it probably ought to work), by tricks in CVSROOT/modules, and alias the existing zsh tree to `zsh-3.1', but renaming the current zsh tree to zsh-3.1 might not be possible. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070