Follow-up Comment #5, bug #68339 (group groff): [comment #4 comment #4:] > I answered with an e-mail instead of using the web page for bug-groff as > I usually do.
Okay. You might want to stick with the Savannah web interface to ensure that your replies are logged in the ticket. > The used version is the master branch with > > commit 1a59f8a2a39e20fa5c7ea25b766b550e210c7560 (HEAD -> master) > Merge: 9e4958fc9 316c9da4a > Author: Bjarni Ingi Gislason <[email protected]> > Date: Sat May 9 13:59:06 2026 +0000 > > Merge branch 'master' of https://git.savannah.gnu.org/git/groff Yes, that's the problem. I have no idea what's in this branch. Not the "master" branch of "https://git.savannah.gnu.org/git/groff";, but **your** "master". Compiler warnings elicited by _your_ master branch are not actionable by GNU _groff_ developers. I repeat my query. Are you willing to re-run your analysis against, say, an unpacked, pristine groff 1.24.1 source archive? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?68339> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
