From: Shachar Shemesh <email@example.com>
To: Linus Torvalds <firstname.lastname@example.org>
Cc: Zack Brown <email@example.com>,
Marcelo Tosatti <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: ChangeLog suggestion
Date: Sat, 26 Apr 2003 21:17:21 +0300 [thread overview]
Message-ID: <3EAACD31.firstname.lastname@example.org> (raw)
Linus Torvalds wrote:
>But both the short-format changelog (the ones posted to linux-kernel) and
>the CVS tree do hide the addresses somewhat.
I'm afraid I did not explain myself clearly. I fear that the format is
both too short, and not descriptive enough. I think taking only the real
name from the email would server both the purpose of searching the list,
and the purpose of understanding who submitted the patch simpler.
The anti spam part was the fact that my email (for the purpose of this
list) is email@example.com, which leaves an awfully undescriptive "lkml"
in CVS. This allows neither searching nor accounting. As I'm sure other
people use the exact same technique when posting to a mailing list,
searching for someone who's email is lkml@* will not even be unique.
I hope my intention was clearer this time.
Open Source integration consultant
Home page & resume - http://www.shemesh.biz/
next prev parent reply other threads:[~2003-04-26 18:05 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
2003-04-26 17:44 ` Shachar Shemesh
2003-04-26 18:06 ` Linus Torvalds
2003-04-26 18:17 ` Shachar Shemesh [this message]
2003-04-26 18:23 ` Larry McVoy
2003-04-26 18:29 ` Jörn Engel
2003-04-26 20:08 b_adlakha
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).