From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: bk-3.2.0 released
Date: Wed, 19 May 2004 11:41:59 -0400 [thread overview]
Message-ID: <c8fuj1$vdi$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040519075128.A19221@infradead.org>
Christoph Hellwig wrote:
> On Tue, May 18, 2004 at 04:32:38PM -0700, Larry McVoy wrote:
>
>>BitKeeper Users,
>>
>>BK/Pro 3.2.0 has been released and is in the BK download area,
>>
>> http://bitmover.com/download
>
>
> And what makes this relevant for lkml? I'm happy BK user, but this just
> seems to be compltely offtopic here..
Announcements regarding kernel tools seem relevant, as is any other tool
change which might affect the kernel creation, maintenence, compilation
or install. Considering the amount of stuff virtually everyone reads
past in this list, reports on features not of interest or 2.4 kernels no
longer used, why did you single out this short and informational message
as worthy of comment?
I personally have a folder of release announcements, even for things I
don't use, just so I can find them quickly if my interest or business
needs change. I wish there was a single release announcements list, but
there isn't, let's keep useful information HERE!
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-05-19 15:37 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
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 [this message]
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='c8fuj1$vdi$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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