linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zack Brown <zbrown@tumblerings.org>
To: Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: ChangeLog suggestion
Date: Fri, 25 Apr 2003 23:21:05 -0700	[thread overview]
Message-ID: <20030426062105.GA1423@renegade> (raw)

Hi Linus, Marcelo,

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.

Be well,
Zack

-- 
Zack Brown

             reply	other threads:[~2003-04-26  6:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-26  6:21 Zack Brown [this message]
2003-04-26  6:52 ` ChangeLog suggestion 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
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=20030426062105.GA1423@renegade \
    --to=zbrown@tumblerings.org \
    --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 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).