From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263777AbTDZGhQ (ORCPT ); Sat, 26 Apr 2003 02:37:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264620AbTDZGhQ (ORCPT ); Sat, 26 Apr 2003 02:37:16 -0400 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:49280 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S263777AbTDZGhQ (ORCPT ); Sat, 26 Apr 2003 02:37:16 -0400 From: John Bradford Message-Id: <200304260652.h3Q6qJmB000386@81-2-122-30.bradfords.org.uk> Subject: Re: ChangeLog suggestion To: zbrown@tumblerings.org (Zack Brown) Date: Sat, 26 Apr 2003 07:52:19 +0100 (BST) Cc: torvalds@transmeta.com (Linus Torvalds), marcelo@conectiva.com.br (Marcelo Tosatti), linux-kernel@vger.kernel.org (Linux Kernel Mailing List) In-Reply-To: <20030426062105.GA1423@renegade> from "Zack Brown" at Apr 25, 2003 11:21:05 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > In each changelog entry, it would be really useful to include the > Message-ID of that email in a regex-parsable location. This way, if the > email was cced to lkml it would be possible for folks to track down the > actual patch. > > I'm not familiar with your scripts, but I'd be surprised if this were very > difficult to implement. At the same time, there are many cases of changelog > entries that read only 'USB' or something equally unhelpful, where there is > little chance that anyone could track down the corresponding patch. Having the > Message-ID in those cases would make all the difference in the world. The changelogs are generated by BitKeeper - couldn't we simply include a link that will let anybody[1] access the relevant changesets? [1] This can be via HTTP, and _doesn't_ require anybody to use BitKeeper in any way. John.