On 2014-10-01 10:29, Alan McKay wrote:
On Tue, Sep 30, 2014 at 4:56 PM, Josh Grosse <j...@jggimi.homeip.net>
wrote:
They happen whenever a fix is backported but not deemed critical
enough
or in wide enough use for errata. Here's the first two I found in
5.5-stable,
there may be others but I stopped looking, since you just wanted a
couple
of examples.
Thanks. How do I go about finding those myself?
Several options to choose from:
1. Update a local working directory from -release to -stable
Start with -release working directory, which can be from CD, or tarball,
or AnonCVS. Update, logging CVS output. Compare patched or updated
modules against errata.
2. Subscribe to the CVS commit log mailing list, and watch for commits
tagged for -stable (OPENBSD_n_m). Compare with errata publication. You
can also subscribe to the Ports CVS commit log mailing list, and note
any -stable port commitments.
3. Keep a local CVSROOT repository with CVSync, which gives you access
to the complete Changelog* history, which you can search. This is
sometimes
more helpful than searching mailing list archives for commits.
I happened to use option 3 for the quick search I conducted for you
yesterday.
CVS commits are also logged via the CVS Web interface at
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ It's an extremely useful
service, and
I use it too, just not not for this sort of generic scan.
