Feb 19 2019
Jan 9 2019
Nov 7 2018
Oct 20 2018
Sep 15 2018
Antoine just gave me the results for an exp-run with this change applied: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231256
Sep 13 2018
Sep 10 2018
@ed can we get this added to the CI work load as a once a week type run? IIRC it takes a 16 core machine about 3 days to run build_option_survey.sh
Sep 9 2018
It looks like I'm quite the forgetful person. In D9169, cem@ tried to solve the same thing. Eventually he abandoned the idea, because we weren't able to accurately implement the __generic() matching to filter out bad calls.
Add logic to explictly make old calls to qsort_r(3) fail.
It's a fair point you two are making: with the change I sent out, code that calls qsort_r() in the existing way will compile without any warnings/errors. This is why I've just changed my patch to add some logic to stdlib.h and libkern.h to detect bad calls, similar to how we dealt with the dirname() / basename() transition (libgen.h). Calls to qsort_r() with the comparator as the last argument will fail explictly.
Sep 8 2018
Sep 3 2018
Sep 1 2018
Uriparser 0.8.6 has been released in the meantime.
Aug 27 2018
Aug 2 2018
Looks good. Thanks a lot for working on this!
Jul 15 2018
Jul 8 2018
Jul 7 2018
Jul 2 2018
Jun 28 2018
Jun 25 2018
Jun 22 2018
Jun 21 2018
Jun 18 2018
Jun 13 2018
Apr 20 2018
Apr 15 2018
Apr 12 2018
Ben: any final thoughts before I commit this?
Apr 9 2018
Process woodsb02's feedback.
Apr 8 2018
Process feedback from kib@.
Don't conditionalize the addition of the pointer.
Always show the <PRI>VERSION. Don't let it depend on LogFacPri.
Apr 7 2018
Apr 6 2018
Oops! Accidentally used the wrong differential revision in the commit message. This was committed as r332100.
Apr 5 2018
Apr 4 2018
Make the scope of what is affected a bit more explicit.
Thanks for your input, Kostik. What do you think about this version?
Extend the UPDATING note.
Add a note to UPDATING regarding this change.
There are some alternatives, such as syslog-ng and rsyslog. Documentation indicates that these also support RFC 5424 properly. I will, however, check this to be sure.
Apr 3 2018
Process feedback provided by kib@.
Make minor changes based on woodsb02's feedback.
Apr 2 2018
Respect RemoteAddDate (-T) for RFC 5424 messages.
Process the excellent feedback given by woodsb02@. Thanks!
Apr 1 2018
Add explicit buffer size to parsemsg_remove_unsafe_characters().
Mar 24 2018
Mar 12 2018
Feb 9 2018
While there, make use of GitHub instead of SourceForge.
Revert unnecessary changs to other ports.
Feb 7 2018
Jan 30 2018
Jan 27 2018
Jan 19 2018
Is there a need to describe how these should be formatted? Can we place multiple initializers on one line, or should they all be placed on a separate one? Tabs before the = to align them?