From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261942AbTDZQh4 (ORCPT ); Sat, 26 Apr 2003 12:37:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262005AbTDZQh4 (ORCPT ); Sat, 26 Apr 2003 12:37:56 -0400 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:27267 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S261942AbTDZQhy (ORCPT ); Sat, 26 Apr 2003 12:37:54 -0400 From: John Bradford Message-Id: <200304261653.h3QGr2I7017000@81-2-122-30.bradfords.org.uk> Subject: Re: ChangeLog suggestion To: john@grabjohn.com (John Bradford) Date: Sat, 26 Apr 2003 17:53:02 +0100 (BST) Cc: torvalds@transmeta.com (Linus Torvalds), john@grabjohn.com (John Bradford), zbrown@tumblerings.org (Zack Brown), marcelo@conectiva.com.br (Marcelo Tosatti), linux-kernel@vger.kernel.org (Linux Kernel Mailing List) In-Reply-To: <200304261650.h3QGof9x016977@81-2-122-30.bradfords.org.uk> from "John Bradford" at Apr 26, 2003 05:50:41 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 > > > The changelogs are generated by BitKeeper - couldn't we simply include > > > a link that will let anybody[1] access the relevant changesets? > > > > Well, yes, the changelogs are generated by BitKeeper, but what gets fed > > into bitkeeper is controlled by some scripts I wrote, which are the ones > > that take the email and munge it into a readable format etc. So by the > > time the thing hits my BK repository, the email headers will all have been > > thrown away, except for "From: " and "Subject: ". So BK never sees the > > full email. > > > > (Even my scripts don't see the full email a large percentage of the time: > > I end up prettifying the emails for actual application by first removing > > things like "Hi Linus, please apply this" etc which are pointless in the > > changelog). > > Oh, I wasn't suggesting trying to preserve a link to the E-Mail via > the scripts->BK chain. > > What I was thinking of was each time you import a patchset from a > [mail | set of mails], BK makes that in to a changeset, which can't be > referenced directy in the changelog, because the changeset's id can > change in the future. Is there no way that BK can generate a > reference to the HTTP interface to bkbits that will remain constant, > and can therefore be included in the changelog, (as an URL to retrieve > a patch from). Even if the patch can't be applied to any particular > tree, it's still something that can be refered to in a mail to LKML, > or similar. Ignore this suggestion, I missed your other mail in this thread - I see now that there isn't a sensible way to do it :-). John.