From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: John Bradford <john@grabjohn.com>,
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 09:50:37 -0700 [thread overview]
Message-ID: <20030426165037.GB14914@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304260931190.2276-100000@home.transmeta.com>
On Sat, Apr 26, 2003 at 09:34:25AM -0700, Linus Torvalds wrote:
> (Even my scripts don't see the full email a large percentage of the time:
> I end up prettifying the emails for actual application by first removing
> things like "Hi Linus, please apply this" etc which are pointless in the
> changelog).
I really wish Marcelo would do this or someone would volunteer to clean
up the change log comments. BitKeeper doesn't have an easy way to
propogate changes to the checkin comments (they are not currently
revision controlled). However, you can change them and someone could
clean up all the crud in the 2.4 tree and we could replace the one
on bkbits with a cleaned up one.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-04-26 16:38 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 [this message]
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=20030426165037.GB14914@work.bitmover.com \
--to=lm@bitmover.com \
--cc=john@grabjohn.com \
--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).