Hi Thayne,
On Thu, Jan 07, 2021 at 02:09:10AM -0700, Thayne McCombs wrote:
> From the output of codespell.
Thanks for this, but I'll ask you a favor, which is to split this into
2 or 3 patches:
- one for the pure documentation, that will have to be backported
since the documentation is user visible and in this essence,
spelling mistakes in the doc can be seen as bugs that deserve being
fixed ; you can use a single patch for all doc-related stuff, that's
OK, just label it as "DOC".
- one for code comments: these ones have zero impact on existing code
and will usually not be backported as they may needlessly annoy users
who maintain their own out-of-tree patches, unless that's needed to
ease backports of later patches. These can be tagged as CLEANUP since
nothing changes for the user (0 byte of output code or package changes).
- possibly a separate one for error messages or anything that is in the
code and is user-visible. These ones will result in code changes that
may have an impact on out-of-tree patches but are fixes that need to
be backported anyway. These ones may be labelled as DOC, CLEANUP, or
"BUG/MINOR" as you see fit. In some cases they may be merged with the
first ones but I tend to prefer that they remain distinct since they
cause a different binary at the end and may occasionally impact some
local regtests some users might have to run before upgrading.
Thanks!
Willy
