Update of bug #67840 (group groff):
Status: None => Confirmed
Assigned to: None => gbranden
Summary: [mm] [doc] [PATCH] Possible typo in documentation of
WA request groff_mm(7) => [PATCH] [mm] typo in documentation of `WA` request
in groff_mm(7)
_______________________________________________________
Follow-up Comment #1:
Good catch! Thanks, Alexis.
Updating tags. I am compelled to document the tag annotations I (and to some
extent other _groff_ developers) use.
* I like to put "[PATCH]" first because tickets with proposed code fixes are
rare and important, and we want to act on them with additional priority when
they exist (and are sound), to encourage contributors.
* Another sort of annotation refers roughly to the "module" of the code
relevant to the report. This is arguably duplicative of the "Category", but
the "Category" is not necessarily visible in all reports when "browsing" in
the Savannah ticket tracker. These tags are pretty close to the same ones I
use in Git commit messages, and for the same reason: the summary lines of Git
commits and the Summary lines of Savannah tickets are both length-limited, and
the file specifications in _groff_'s Git repository can be lengthy.
Here's an example.
src/preproc/grn/tests/passes-through-input-with-eighth-bit-set.sh
In length-limited contexts. this file name leaves little room to say anything
else, thus "[grn]".
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67840>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
