From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23581 invoked from network); 13 Oct 1999 18:42:55 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Oct 1999 18:42:55 -0000 Received: (qmail 13286 invoked by alias); 13 Oct 1999 18:42:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8240 Received: (qmail 13278 invoked from network); 13 Oct 1999 18:42:47 -0000 Date: Wed, 13 Oct 1999 14:42:33 -0400 From: Clint Adams To: Bart Schaefer Cc: zsh-workers@sunsite.auc.dk Subject: Re: Module idea to help developers Message-ID: <19991013144233.A23715@dman.com> References: <991013162014.ZM14485@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre3i In-Reply-To: <991013162014.ZM14485@candle.brasslantern.com> > It would be great if zsh could report something about what patches it has > applied to it. We could make a little module that implements a special > array parameter `patches', and stick a line in that module to identify each > patch, so that you could "print $patches" to see what was up. 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. What you're proposing seems more suited for patches that won't be incorporated.