On Thu, Sep 03, 2026 at 09:33:46AM -0700, Randy Dunlap wrote: > >> Nguyen Duc Thinh (5): > >> Documentation: process: Clean up grammar, tone, and contractions in > >> core files > >> Documentation: process: Clean up grammar and tone in next guide files > >> Documentation: process: Refine language, tone, and grammar in > >> subsequent files > >> Documentation: process: Refine language, tone, and grammar in > >> subsequent files > >> Documentation: process: Clean up grammar and tone across multiple > >> files > > > > Output of 'b4 shazam': > > > > ... > > Applying: Documentation: process: Clean up grammar, tone, and contractions > > in core files > > Applying: Documentation: process: Clean up grammar and tone in next guide > > files > > Applying: Documentation: process: Refine language, tone, and grammar in > > subsequent files > > Applying: Documentation: process: Refine language, tone, and grammar in > > subsequent files > > Applying: Documentation: process: Clean up grammar and tone across multiple > > files > > /home/user/Projects/linux/.git/rebase-apply/patch:72: trailing whitespace. > > License (about which more will be said below). The author is not a > > warning: 1 line adds whitespace errors. > > /home/user/Projects/linux/.git/rebase-apply/patch:244: trailing whitespace. > > Which is nice, since there is no more insanity in the form of fake-generic > > warning: 1 line adds whitespace errors. > > /home/user/Projects/linux/.git/rebase-apply/patch:261: trailing whitespace. > > rare cases, an AI assistant capable of finding a bug is capable of > > fixing it. > > /home/user/Projects/linux/.git/rebase-apply/patch:262: trailing whitespace. > > Fixes written within the same session used to identify the bug will > > /home/user/Projects/linux/.git/rebase-apply/patch:263: trailing whitespace. > > generally lead to better and more accurate fixes as the LLM's reasoning > > /home/user/Projects/linux/.git/rebase-apply/patch:282: trailing whitespace. > > - Within two weeks, a representative of this group will communicate the > > warning: 4 lines add whitespace errors. > > > > Should we handle with whitespace? > > No, the trailing whitespace should be fixed (i.e., deleted) > and then resend the patches.
Right, I was actually trying to gently point out that the trailing whitespace should be fixed. ;-) This should be caught easily by checkpatch.pl, or simply by running b4 prep --check, I guess. Better run it before sending out next time. Thanks.
