All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: Matti Aarnio <matti.aarnio@zmailer.org>,
	Chris Howells <chris@chrishowells.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: linux-kernel-announce?
Date: Mon, 1 Oct 2001 14:09:58 -0400	[thread overview]
Message-ID: <20011001140958.D24491@borg.org> (raw)
In-Reply-To: <20011001164720Z275269-761+14414@vger.kernel.org> <20011001200045.F1144@mea-ext.zmailer.org> <20011001195158.D1288@pasky.ji.cz>
In-Reply-To: <20011001195158.D1288@pasky.ji.cz>; from pasky@pasky.ji.cz on Mon, Oct 01, 2001 at 07:51:58PM +0200

To find out about new kernels I suggest two techniques.

Low Time Requirement: Go to Linux Weekly News <http://lwn.net> at the
end of every week.  They do a good summary of what is up in kernel
efforts.  

Large Time Requirement: Read the kernel mailing list.  Even if you
miss an announcement by Linus or Alan or Andrea et al, you will see
others making postings about every significant kernel.


-kb, the Kent who has taken to compiling most of the kernels that come
out.

  reply	other threads:[~2001-10-01 18:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 16:47 linux-kernel-announce? Chris Howells
2001-10-01 16:57 ` linux-kernel-announce? André Dahlqvist
2001-10-01 17:00 ` linux-kernel-announce? Matti Aarnio
2001-10-01 17:51   ` linux-kernel-announce? Petr Baudis
2001-10-01 18:09     ` Kent Borg [this message]
2001-10-01 14:54       ` linux-kernel-announce? Rob Landley
2001-10-02 18:51   ` linux-kernel-announce? Chris Howells
2001-10-01 19:48 ` linux-kernel-announce? Mike Fedyk
2001-10-02  1:01   ` linux-kernel-announce? Rob Landley
2001-10-02  5:27     ` linux-kernel-announce? john slee
2001-10-02  7:21     ` linux-kernel-announce? Russell King
2001-10-02 18:56     ` linux-kernel-announce? Chris Howells
2001-10-02 18:54   ` linux-kernel-announce? Chris Howells

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=20011001140958.D24491@borg.org \
    --to=kentborg@borg.org \
    --cc=chris@chrishowells.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.