From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: bk-3.2.0 released
Date: Wed, 19 May 2004 07:23:34 -0700 [thread overview]
Message-ID: <40AB6DE6.2090005@backtobasicsmgmt.com> (raw)
In-Reply-To: <20040519141648.GB18977@work.bitmover.com>
Larry McVoy wrote:
> I don't see the problem. What's the big deal about a post that says a
> new version of a widely used tool is available? If someone posted that
> there is a new version of gcc available is that off topic?
No, this list gets monthly (if not more often) announcements of new
versions of the "shortlog" tool and the other related tool, both of
which are used pretty much exclusively by Linus and Marcelo. I haven't
seen anyone complain about those, and their frequency is 10 times that
of the BK update announcements.
next prev parent reply other threads:[~2004-05-19 14:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 23:32 bk-3.2.0 released Larry McVoy
2004-05-19 6:51 ` Christoph Hellwig
2004-05-19 14:02 ` Larry McVoy
2004-05-19 14:11 ` Jan-Benedict Glaw
2004-05-19 14:16 ` Larry McVoy
2004-05-19 14:23 ` Kevin P. Fleming [this message]
2004-05-19 14:36 ` John Bradford
2004-05-19 18:47 ` Tomas Szepe
2004-05-19 14:26 ` Jan-Benedict Glaw
2004-05-19 14:48 ` Larry McVoy
2004-05-19 15:00 ` Jan-Benedict Glaw
2004-05-19 15:09 ` Larry McVoy
2004-05-19 16:10 ` Nicolas Pitre
2004-05-19 20:06 ` Valdis.Kletnieks
2004-05-19 21:20 ` Stan Bubrouski
2004-05-19 14:33 ` Christoph Hellwig
2004-05-19 14:32 ` Christoph Hellwig
2004-05-19 14:34 ` John Bradford
2004-05-19 15:41 ` Bill Davidsen
2004-05-20 3:10 ` Jeff Sipek
2004-05-29 9:54 ` Vojtech Pavlik
2004-05-29 13:04 ` Larry McVoy
2004-05-29 13:15 ` Hugo Mills
2004-05-29 13:20 ` Larry McVoy
2004-05-29 15:47 ` Larry McVoy
2004-05-29 20:13 ` Bryan O'Sullivan
2004-05-30 3:59 ` David Lang
2004-05-29 13:20 ` Vojtech Pavlik
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=40AB6DE6.2090005@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.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