Thanks, Ed, but where do I find this? uname -a" gives me
stable/13-007101f87. For a while I was seeing a hyphenated number prefixed
with a 'c' and I had assumed that that number was the sequence. The full
hash from the logs just is a long hex number. As usual with git stuff, I'm
still very confused. After decades with a common paradigm with RCS CVS and
SVN, git is fundamentally very different and old terminology does not
really align as git is designed from a very different perspective.
I have read the little mini-guide Warner wrote as well as a couple of web
tutorial, but the web tutorials are really about running your own repo on
github or gitlab, not using a repo as a source for distributions. I'm still
a long way from having a real clue.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Wed, Feb 24, 2021 at 12:06 PM Ed Maste <emaste at freebsd.org> wrote:
> On Wed, 24 Feb 2021 at 12:35, Kevin Oberman <rkoberman at gmail.com>
wrote:
> >
> > In the svn days, I could just look at my svn revision to check on
> whether a
> > security patch was required. Now I have a git hash. I have no idea how
to
> > tell if my system running 13-STABLE of a few days ago has the patch.
>
> Thanks for posting this question. I see some useful information in
> other replies to this thread and we'll want to make sure that makes
> its way to appropriate documentation.
>
> For future advisories we should also report the commit count
> associated with the fix; this is a monotonically-increasing number and
> is reported in the uname.
>
> If you build stable/13 right now you would get
> "stable/13-n244668-4664afc05402", and the fix in
> 894360bacd42f021551f76518edd445f6d299f2e corresponds to n244572.
> 244668 being larger than 244572 indicates that the fix is included.
>
> These counts are not unique across different branches; you can only
> compare counts for the same branch.
>