From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Identify security-related patches
Date: Thu, 02 Sep 2004 09:08:17 +0200 [thread overview]
Message-ID: <4136C6E1.4090404@bio.ifi.lmu.de> (raw)
Hi,
is there an easy way to identify all security-related patches out of the
mass of patches floating around on linux.bkbits.net or the kernel bugzilla?
I'm running 2.6.8.1 and would like to keep it as stable as possible, thus,
only apply security patches. Currently I'm searching for "security" and
alike on bitkeeper, but there seems to be no consistent marking.
For instance, it would be nice if all security fixes contained a consistent
marker like "[SECURITY]" in the changeset comments (like the reiserfs xattr/acl
patch does), so that it would be easy to identify them. Or setting some kind
of flag to such patches (I've no idea what bitkeeper allows one to do...).
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
next reply other threads:[~2004-09-02 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 7:08 Frank Steiner [this message]
2004-09-02 18:48 ` Chris Wright
2004-09-02 19:12 ` Valdis.Kletnieks
2004-09-02 20:22 ` Florian Weimer
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=4136C6E1.4090404@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--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
all inboxes | Powered by JetHome®