From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25600 invoked from network); 8 Oct 1997 16:52:56 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 8 Oct 1997 16:52:56 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id MAA03014; Wed, 8 Oct 1997 12:45:58 -0400 (EDT) Resent-Date: Wed, 8 Oct 1997 12:45:58 -0400 (EDT) Message-Id: <199710081646.MAA02053@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <199710081443.KAA27464@math.gatech.edu> X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.0b6.3) From: Timothy J Luoma Date: Wed, 8 Oct 97 12:46:40 -0400 To: zsh-workers@math.gatech.edu Subject: Re: Current state of 3.1.2 References: <199710081443.KAA27464@math.gatech.edu> Resent-Message-ID: <"S7TVT2.0.1l.6ZxEq"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3563 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Author: Bruce Stephens Original-Date: Wed, 08 Oct 1997 15:43:38 +0100 Message-ID: <199710081443.KAA27464@math.gatech.edu> > Perhaps there could be some way of archiving just the patches posted to > zsh-workers, in an order that they could be applied to the latest test > version? This would typically just involve those sending patches to put an > indication in the header of their mail ("Subject: PATCH ...", or > something), with the occasional intervention needed when people supply > incompatible patches. Maybe I can chime in here. It would be child's play for me to set this up somewhere under the ZSH web page @ PEAK.org (http://www.peak.org/zsh/). I already have an email-2-html setup there. The easiest way would be if we could agree to send patches to 'zsh@peak.org' (another address for me). That way no one has to remember any special Subjects and it would be easy enough to do (just CC that address when you send in a patch). Upside: no non-Patches would show up, trivial to maintain Downside: if you don't remember to send it there, it doesn't get added If it was deemed better to use a certain Subject: header such as PATCH that would be fine too Upside: only have to remember one address Downside: have to remember the right Subject header TjL