From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com (John Bradford)
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)
Subject: Re: ChangeLog suggestion
Date: Sat, 26 Apr 2003 17:53:02 +0100 (BST) [thread overview]
Message-ID: <200304261653.h3QGr2I7017000@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <200304261650.h3QGof9x016977@81-2-122-30.bradfords.org.uk> from "John Bradford" at Apr 26, 2003 05:50:41 PM
> > > 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.
next prev parent reply other threads:[~2003-04-26 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 6:21 ChangeLog suggestion Zack Brown
2003-04-26 6:52 ` John Bradford
2003-04-26 15:12 ` Zack Brown
2003-04-26 17:28 ` Arjan van de Ven
2003-04-26 16:34 ` Linus Torvalds
2003-04-26 16:50 ` Larry McVoy
2003-04-26 16:50 ` John Bradford
2003-04-26 16:53 ` John Bradford [this message]
2003-04-26 17:07 ` Zack Brown
2003-04-26 16:29 ` Linus Torvalds
2003-04-26 17:44 ` Shachar Shemesh
2003-04-26 18:06 ` Linus Torvalds
2003-04-26 18:17 ` Shachar Shemesh
2003-04-26 18:23 ` Larry McVoy
2003-04-26 18:29 ` Jörn Engel
2003-04-26 20:08 b_adlakha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304261653.h3QGr2I7017000@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=zbrown@tumblerings.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).