https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238309

--- Comment #2 from Alexey Dokuchaev <da...@freebsd.org> ---
Sometimes I do "svn blame" (as e.g. in bug #238167), sorry I didn't add it this
time, here it is:

> 106101    phk       if (indent == NULL) {
> 106101    phk               sbuf_printf(sb, " i %u", pp->index);
> 106101    phk               sbuf_printf(sb, " o %ju",
> 106101    phk                   (uintmax_t)gsp->slices[pp->index].offset);
> 106101    phk               return;
> 106101    phk       }
When commit is fairly recent (this one is not), I'd usually reply to the
committer directly (via the original commit mail).

> I don't want to miss any of these issues (and I might).
I think you've missed bug #238194. :-)

> Does PVS make its output available in a report format we could share
> with developers more broadly?
PVS is not doing these runs, I'm doing them myself.  I've posted a few messages
to svn-src-head@ a week ago, with a link to a full log, you can find it in my
$HOME at freefall (pvs-kernel-filtered-2019-05-28.log.xz).

> I understand it includes false positives, but I imagine it would be
> a good resource for many to look at nontheless.
I hope so; I do keep a list of false positives that people send me to reduce
the noise in subsequent runs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to