public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Bubrouski <stan@ccs.neu.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: bk-3.2.0 released
Date: Wed, 19 May 2004 17:20:43 -0400	[thread overview]
Message-ID: <1085001643.9697.10.camel@duergar> (raw)
In-Reply-To: <200405192006.i4JK6Hv8004808@turing-police.cc.vt.edu>

Guys,

Honestly this crap is getting very silly even though you are all
serious.  People announce things on this list all the time that
are not really a part of the kernel but affect development, and
with the traffic on this list anyways, I don't see how Larry
announcing a new release of BitKeeper is offtopic or innappropriate.

Furthermore, it seems like any time Larry posts anything not in a thread
starting with [patch] or [oops] someone goes off on some political or
otherwise rant and its getting really really old.  The threads become
long and littered with opinions that contribute nothing but someone's
$0.2 in a case where it makes no difference at all except to the
bandwith the posts complaining about posts wastes.

Lighten up I guess is all I'm saying.

-sb


On Wed, 2004-05-19 at 16:06, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 19 May 2004 16:26:56 +0200, Jan-Benedict Glaw said:
> > 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? =20
> > 
> > Yes, it was. Even miscompilation reports are mostly OT, since they
> > should go to GCC's bugzilla.
> 
> Given the number of times (it's well past non-zero) we've changed around kernel
> source in order to work around a bug in one or another widely-distributed
> release of gcc, I think miscompile reports *are* on topic.
> 
> I seem to remember that gcc 3.4 did oddness with inlining strcpy that resulted
> in a source tweak to lib/strings.c not too long ago, as just one example...
> 
> And there was the "read/write constraints and registers" warning recently...
> 
> And there was.... you get the idea...
> 


  reply	other threads:[~2004-05-19 21:20 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
2004-05-19 16:10                 ` Nicolas Pitre
2004-05-19 20:06           ` Valdis.Kletnieks
2004-05-19 21:20             ` Stan Bubrouski [this message]
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=1085001643.9697.10.camel@duergar \
    --to=stan@ccs.neu.edu \
    --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