From: Shachar Shemesh <lkml@shemesh.biz>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Zack Brown <zbrown@tumblerings.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ChangeLog suggestion
Date: Sat, 26 Apr 2003 20:44:40 +0300 [thread overview]
Message-ID: <3EAAC588.9010806@shemesh.biz> (raw)
In-Reply-To: <Pine.LNX.4.44.0304260924190.2276-100000@home.transmeta.com>
Linus Torvalds wrote:
>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.
>
>
Slightly OT:
Note that the "author" info is only semi readable from CVS. It contains
just the user part of the email address (in my case - "lkml" for spam
reasons - hardly a unique identifier). I'm told that under BK it has the
full email, so I'm not sure where that stands there.
This does mean that under CVS, this info is not searchable, nor even
guarenteed unique.
Shachar
--
Shachar Shemesh
Open Source integration consultant
Home page & resume - http://www.shemesh.biz/
next prev parent reply other threads:[~2003-04-26 17:32 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 [this message]
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=3EAAC588.9010806@shemesh.biz \
--to=lkml@shemesh.biz \
--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).