From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19188 invoked by alias); 24 Jan 2012 19:32:46 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30120 Received: (qmail 350 invoked from network); 24 Jan 2012 19:32:33 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 Received-SPF: neutral (ns1.primenet.com.au: 209.85.212.171 is neither permitted nor denied by SPF record at ntlworld.com) X-ProxyUser-IP: 86.6.29.42 Date: Tue, 24 Jan 2012 19:06:16 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: ChangeLog generation (was: Re: Next release) Message-ID: <20120124190616.44ae8cc0@pws-pc.ntlworld.com> In-Reply-To: <87r4yps14w.fsf@ft.bewatermyfriend.org> References: <20111209141117.52c1e37a@pwslap01u.europe.root.pri> <87iplpzfr0.fsf@ft.bewatermyfriend.org> <20111210171956.32b37a06@pws-pc.ntlworld.com> <877h24xmhh.fsf@ft.bewatermyfriend.org> <20111210194648.2ce77de2@pws-pc.ntlworld.com> <87r4yps14w.fsf@ft.bewatermyfriend.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 X-Gm-Message-State: ALoCoQnYJoQ/NeHvo3bnS3j9mIjGUBARp+87TAcYydnZeN7QjUzK2RPBuWSvoX+lXXCRqDY+La1Q Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 24 Jan 2012 14:03:59 +0100 Frank Terbeck wrote: > I had some spare time, being on a train, and I came up with this: > > > > That should be good enough (minus bugs, obviously). That's useful, thanks. We still need some way of associating the mailing list posting with the change set, which is a bit of a puzzle since you are likely to commit it to your local repository first. It doesn't need to be in comments (I couldn't see any way of updating them when pushing), it could be in some other metadata, so there may well be some workaround. We're sunk without it, though, since tracing changes back to the discussion about it on the mailing list is crucial for working out the intention behind changes. Ultimately this is no more than the usually necessity for tracking from an archive to a bug database (as with Perforce's notion of jobs, for example, which would do this nicely), so somebody's bound to have thought about it. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/