From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28748 invoked from network); 14 Oct 1999 03:48:51 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Oct 1999 03:48:51 -0000 Received: (qmail 18429 invoked by alias); 14 Oct 1999 03:48:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8242 Received: (qmail 18420 invoked from network); 14 Oct 1999 03:48:44 -0000 From: "Bart Schaefer" Message-Id: <991014034839.ZM15300@candle.brasslantern.com> Date: Thu, 14 Oct 1999 03:48:39 +0000 In-Reply-To: <19991013144233.A23715@dman.com> Comments: In reply to Clint Adams "Re: Module idea to help developers" (Oct 13, 2:42pm) References: <991013162014.ZM14485@candle.brasslantern.com> <19991013144233.A23715@dman.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: Module idea to help developers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 13, 2:42pm, Clint Adams wrote: } Subject: Re: Module idea to help developers } } > We could make a little module that implements a special array } > parameter `patches', and stick a line in that module to identify } > each patch } } Assuming all these packages will end up in the source, increasing } release frequency or providing CVS snapshots (with the date } automatically appended to the version number) would help a bit. I agree, but that presupposes a CVS archive, which we've made no progress on establishing over the last two or three months that it's been under serious consideration. The Sunsite Denmark folks are completely silent (I don't think they're even looking at the zsh-*-owner mail right now) and PWS is apparently offline for an indeterminate time. I was hoping for something quick but effective in the meantime. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com