[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 --- Comment #7 from Ed Maste --- There are two possible follow-on changes that could be made: - Add a note in the man page that the flags are case insensitive but by convention are typically uppercase. - Switch the switch statement to

[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 --- Comment #6 from Ed Maste --- Thanks for the thorough chase through the rabbit hole! I've merged the patch as it makes sense for the man page to be consistent. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=a8f86ecd6104b1f127b426be278a9031789b4413 commit a8f86ecd6104b1f127b426be278a9031789b4413 Author:

[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 --- Comment #4 from Joshua Kinard --- (In reply to Joshua Kinard from comment #3) Why is it always the little things that hide the deepest of rabbit holes? I dug back into FreeBSD's cgit history, and it looks like the 'p'/'P' flag (take

[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 --- Comment #3 from Joshua Kinard --- (In reply to Ed Maste from comment #2) The switch statement is changing the flag characters to lower case before it checks them: > for (; q && *q && !isspacech(*q); q++) { > switch

[Bug 279303] usr.sbin/newsyslog: Fix case of the 'P' flag in newsyslog.conf's manpage

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279303 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from

Problem reports for b...@freebsd.org that need special attention

2024-05-26 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 279285] no sound on stable/14 with vchans disabled and bitperfect setup.

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279285 --- Comment #10 from Christos Margiolis --- (In reply to Oleh Vinichenko from comment #8) So, I have one or two commits after 8771127d75a1295dd32abd0022ff3750bc564706 in mind that could potentially be the culprit, but I want to ask the

[Bug 279285] no sound on stable/14 with vchans disabled and bitperfect setup.

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279285 --- Comment #9 from Oleh Vinichenko --- also, are the commits related, or independent of each other? in latter case it make sense to go through every commit one by one. -- You are receiving this mail because: You are the assignee for the

[Bug 279285] no sound on stable/14 with vchans disabled and bitperfect setup.

2024-05-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279285 --- Comment #8 from Oleh Vinichenko --- unfortunately, very latest changes did not change the situation. i will start reverting of /usr/src before commit 8771127d75a1295dd32abd0022ff3750bc56470 is there more robust way of doing it? because