From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22585 invoked from network); 13 Oct 1999 16:20:29 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Oct 1999 16:20:29 -0000 Received: (qmail 26616 invoked by alias); 13 Oct 1999 16:20:24 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8238 Received: (qmail 26608 invoked from network); 13 Oct 1999 16:20:22 -0000 From: "Bart Schaefer" Message-Id: <991013162014.ZM14485@candle.brasslantern.com> Date: Wed, 13 Oct 1999 16:20:14 +0000 X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Module idea to help developers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I don't have time to do this myself right now, but: 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. We'd need a convention of some kind -- either it could be up to the patch- applier to insert the article number by hand, or (better) the patch-maker should supply a hunk for that module that adds a string he's made up. Such a hunk would be likely to fail if some prerequisite patch was not present (I suppose it would also be likely to fail in some cases of simultaneous unrelated patching by two developers, but that would be easily resolved), thus giving a clue about mistakes. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com