[U-Boot] speaking of fixing spelling mistakes and stuff like that ...

[Robert P. J. Day]

  as i dig through the u-boot code, i frequently run across spelling
mistakes and other apparently non-functional issues, but i don't want
to pollute the list with patch after patch of trivial fixups, so i
started a local git branch called "typos" to which i add these things
and, eventually, i'll just send it in as one big patch, which inspires
two questions.

  first, is it still considered bad form to submit patches which might
touch numerous subsystems all over the code base? certainly, actual
functional changes shouldn't do that, but what about aesthetic fixes?
is it still necessary to CC each subsystem maintainer affected if
there are, like, a dozen of them? (whenever i find a particular typo,
i do a code-wide grep to nail all of them and add all of them to the
typos branch, so i could find them all over the place.) what to do?

  and second, is it worth (like the kernel folks do) adding a
"trivial" branch (in kernel case, email "trivial at kernel.org"), which
could collect trivial things like this off to the side, and eventually
just add it all as one big patch?

  i'm happy to send in typo fixes, but i have no interest in
generating all that churn if there's a better way.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================