what is the best way to send in a patch for quite a number of
tree-wide (ie., unrelated) typos throughout the source? almost all of
them are innocuous -- either comments or in printed strings, so they
*shouldn't* break anything.
these days, i have a separate "typos" git branch where i just
collect typos i run across, and keep rebasing it against "master" to
stay up to date. and since this appears to be the u-boot merge window,
i figure now is a good time to send it in. but, as i said, it's spread
all over the tree, so is a single patch even a good idea, or should i
try to break it into smaller, bite-size pieces?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
