From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21381 invoked from network); 23 Apr 2001 16:26:31 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 23 Apr 2001 16:26:31 -0000 Received: (qmail 11537 invoked by alias); 23 Apr 2001 16:26:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14071 Received: (qmail 11512 invoked from network); 23 Apr 2001 16:26:10 -0000 From: "Bart Schaefer" Message-Id: <1010423162458.ZM14874@candle.brasslantern.com> Date: Mon, 23 Apr 2001 16:24:57 +0000 In-Reply-To: <000701c0cbb1$4662bda0$21c9ca95@mow.siemens.ru> Comments: In reply to "Andrej Borsenkow" "What about this? (was: RE: Zsh broken after the latest build patches)" (Apr 23, 8:53am) References: <000701c0cbb1$4662bda0$21c9ca95@mow.siemens.ru> X-Mailer: Z-Mail (5.0.0 30July97) To: "ZSH Workers Mailing List" Subject: Re: What about this? (was: RE: Zsh broken after the latest build patches) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 23, 8:53am, Andrej Borsenkow wrote: } Subject: What about this? (was: RE: Zsh broken after the latest build patc } } > I backed out the following and now zsh works again. } > } > 2001-04-19 Clint Adams } } I meant, in my local version, not in CVS of course. The problem is, I } currently cannot even update cvs ... I agree that we should either back this out entirely, or branch for the 4.0.1 release and back it out on the branch. Andrej, is is possible to back those patches out simply by returning to an earlier CVS revision of the files, or have some of the other termcap or terminfo config changes gotten mised in so the shared linking changes have to be backed out separately? If returning to an earlier revision is sufficient, we can simply create the branch off those revisions, else we'll have to branch from the current state and then back them out. If the consensus is to branch, the recommended procedure is to first tag (without -b) the pre-branch revisions as the "branch point" and then do the actual branch tag (with -b). This makes it easier to identify the common ancestor should code have to be merged onto or from the branch. I can deal with this if necessary. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net