Hi Bjarni, On 2025-01-30 02:39, Bjarni Ingi Gislason wrote: > Package: libcap-dev > Version: 1:2.66-5+b1 > Severity: minor > Tags: patch > > * What led up to the situation? > > Checking for defects with a new version > > test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man > page"
thank you for submissions. I was just going to apply these man page fixes, but it seems that the vast majority of changes are introductions of unnecessary line breaks. For example, from cap_copy_ext.3.diff: > -would require when converted by > +would require > +when converted by I haven't noticed the exact pattern for when this happens, other than punctuation always seems to cause a break. From the same diff: > -into the capability state, converting, if necessary, the data from a > -contiguous, persistent format to an undefined, internal format. Once > -copied into internal format, the object can be manipulated by the capability > +into the capability state, > +converting, > +if necessary, > +the data from a contiguous, > +persistent format to an undefined, > +internal format. > +Once copied into internal format, > +the object can be manipulated by the capability I wouldn't mind applying this regardless, but as I feed patches back upstream, I can't really justify sending them as as-is. Would it be possible for you to check in your script where these line breaks come from? Otherwise, I can just extract the actual fixes. Best, Christian
