> On Mar 6, 2017, at 19:31, Rodney W. Grimes <free...@pdx.rh.cn85.dnsmgr.net> > wrote:
… > I am less concered about fixing this and more concerned about making sure you > understood what the actual sytle.Makeilfe(9) rules are becuase it appeared > that given the counter style changes you thought there should be no white > space after VAR= in a Makefile. > > You probably understand that better than most and this is just a poor > choice of words in the commit message. I was intentionally fixing single space in leading whitespace in this commit along with unnecessary/incorrect trailing whitespace. That’s all I was trying to do, and I suppose the style.Makefile(9) portion of the commit message was overkill—technically it was fixing as little as possible so my eyes didn’t hurt whenever I opened the Makefile with vim, which also suited this requirement. So yes, "opportunistic whitespace cleaning to fix my eyes bleeding from the red colorization from my editor — vim” might have been more accurate. -Ngie
signature.asc
Description: Message signed with OpenPGP using GPGMail
