All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zack Brown <zbrown@tumblerings.org>
To: John Bradford <john@grabjohn.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ChangeLog suggestion
Date: Sat, 26 Apr 2003 08:12:00 -0700	[thread overview]
Message-ID: <20030426151200.GA6743@renegade> (raw)
In-Reply-To: <200304260652.h3Q6qJmB000386@81-2-122-30.bradfords.org.uk>

Hi John,

On Sat, Apr 26, 2003 at 07:52:19AM +0100, John Bradford wrote:
> > 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.

That would be ideal.

Be well,
Zack

> 
> John.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Zack Brown

  reply	other threads:[~2003-04-26 15:00 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20030426151200.GA6743@renegade \
    --to=zbrown@tumblerings.org \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.