From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: bk-3.2.0 released
Date: Wed, 19 May 2004 08:09:49 -0700 [thread overview]
Message-ID: <20040519150949.GA8584@work.bitmover.com> (raw)
In-Reply-To: <20040519150040.GR1912@lug-owl.de>
On Wed, May 19, 2004 at 05:00:40PM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2004-05-19 07:48:52 -0700, Larry McVoy <lm@bitmover.com>
> wrote in message <20040519144852.GC18977@work.bitmover.com>:
> > On Wed, May 19, 2004 at 04:26:56PM +0200, Jan-Benedict Glaw wrote:
> > > On Wed, 2004-05-19 07:16:48 -0700, Larry McVoy <lm@bitmover.com>
> > > wrote in message <20040519141648.GB18977@work.bitmover.com>:
> > > > 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?
> > >
> > > Yes, it was. Even miscompilation reports are mostly OT, since they
> > > should go to GCC's bugzilla.
> >
> > Sigh. This strikes me as "aha, Larry's posted something, let's see if
> > we can get him hooked on some trollbait, that would be fun, it's been
> > a while!"
>
> Not at all! You *do* post useful/helpful/serious/whatnot emails (eg.
> those about the corruption-at-page's-end topic). It's just that I like
> to see noise on this list going down, which includes announcments eg. of
> binutils/gcc, bitkeeper, but also the constant announcments for
> yet-some-more-email-addresses-added patches for some rarely used script.
Some people complain that we don't announce BK releases and some people
complain that we do. Given that we do a release about twice a year I
think complaining about it is over the top. I'm quite happy to stop
announcing it here but the cost of that is I'll just turn off support
for the older releases on openlogging.org and bkbits.net. That's not
very polite to the BK users (it's completely legal, you are supposed
to stay current under the terms of the BKL) but it would keep the list
free of these oh-so-annoying and oh-so-frequent posts. See the tradeoff?
Whether you do or don't, I thought about this and felt it was better
to post than to not post. If you had been in my position I suspect
you'd do the same thing. So how about we let this little tempest in
a teapot die now? I'm sure we have better things to do with our time.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2004-05-19 15:11 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
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 [this message]
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=20040519150949.GA8584@work.bitmover.com \
--to=lm@bitmover.com \
--cc=hch@infradead.org \
--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