public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Greg KH <greg@kroah.com>,
	nick@linicks.net, Adrian Bunk <bunk@stusta.de>,
	Ingo Oeser <ioe-lkml@rameria.de>,
	Chris Wright <chrisw@sous-sol.org>,
	Maciej Soltysiak <solt2@dns.toxicfilms.tv>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.16
Date: Mon, 15 May 2006 10:57:55 -0700	[thread overview]
Message-ID: <20060515175755.GV25010@moss.sous-sol.org> (raw)
In-Reply-To: <20060514051729.GL11191@w.ods.org>

* Willy Tarreau (willy@w.ods.org) wrote:
> One compromise might be to post the full changelog in the announcement
> in addition to the shortlog. But I agree that security fixes are rarely
> well documented by their authors, and CVE descriptions are sometimes
> rather obscure :-(

My preference is to leave things concise.  If one has a question, the
CVE and the full Changelog are pretty easy to obtain and read.

thanks,
-chris

  reply	other threads:[~2006-05-15 17:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  2:25 Linux 2.6.16.16 Chris Wright
2006-05-11  2:29 ` Chris Wright
2006-05-11 10:34 ` Maciej Soltysiak
2006-05-11 11:07   ` Nick Warne
2006-05-11 16:50   ` Daniel Barkalow
2006-05-11 17:33   ` Chris Wright
2006-05-11 18:03     ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51       ` Winn Johnston
2006-05-13 15:35     ` Linux 2.6.16.16 Ingo Oeser
2006-05-13 15:56       ` Adrian Bunk
2006-05-13 17:29         ` Nick Warne
2006-05-14  3:59           ` Greg KH
2006-05-14  5:17             ` Willy Tarreau
2006-05-15 17:57               ` Chris Wright [this message]
2006-05-14  7:46             ` Maciej Soltysiak
2006-05-15 16:30               ` Greg KH

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=20060515175755.GV25010@moss.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    --cc=solt2@dns.toxicfilms.tv \
    --cc=willy@w.ods.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