archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Zack Brown <>
Cc: Marcelo Tosatti <>,
	Linux Kernel Mailing List <>
Subject: Re: ChangeLog suggestion
Date: Sat, 26 Apr 2003 09:29:07 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20030426062105.GA1423@renegade>

On Fri, 25 Apr 2003, Zack Brown wrote:
> I'm not familiar with your scripts, but I'd be surprised if this were very
> difficult to implement.

Well, the scripts can take it, but quite frankly I'd rather not clutter 
the changelogs up with crud that really doesn't matter.

The thing is, the stuff that already _is_ in the changelog is certainly 
enough to identify the email if you just have a reasonable search engine. 
You have author, comments and diff, and if that isn't enough to identify 
the thing then something is wrong.

Also, _most_ of the patches by far end up coming as personal emails, and
while they have often shown up on linux-kernel in _some_ way, it won't be
the same email that got sent to me. The email that showed up on the
mailing list will often have been of the type "please test this out and if
it works for you I'll send it to Linus", or it will have been posted by
the original author and then the actual patch made it to me either through
somebody elses BK tree _or_ through a person like Andrew Morton or Alan

In other words, what you ask for is ugly (yes, I actually look at the 
output of "bk changes") _and_ not very useful.


  parent reply	other threads:[~2003-04-26 16:16 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
2003-04-26 17:07     ` Zack Brown
2003-04-26 16:29 ` Linus Torvalds [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).