Hi! devs, Apologize for the trouble. I am using PyScripter, as Joe says "PyScripter creates the changes by trimming trailing white spaces<https://www.google.co.uk/search?q=pyscripter+trailing+spaces&oq=pyscripter+trailing+spaces&aqs=chrome.0.69i57j69i60.5419j0&sourceid=chrome&ie=UTF-8#sclient=psy-ab&q=pyscripter+trim+trailing+spaces&oq=pyscripter+trim+trailing+spaces&gs_l=serp.3...134352.134992.0.135206.5.5.0.0.0.3.215.815.0j1j3.4.0....0.0..1c.1.20.psy-ab.27nDEBjyY7Y&pbx=1&bav=on.2,or.r_qf.&bvm=bv.49784469%2Cd.cGE%2Cpv.xjs.s.en_US.MpiVkF51mpA.O&fp=79a2a23189da394e&biw=1200&bih=1825>, ie a space or tab at the end of lines or a space or tab in an empty line. It does that the moment you open a file", whitespaces would be committed with the changes.
Any suggestions to avoid this happen? And, may I ask how do you generate codes, devs? Cheers! Hua 2013/7/25 Joachim Dreimann <[email protected]> > Hua, > > I believe Ryan mentioned before that whitespace changes add a lot of noise > to your commits, making it difficult to tell what you actually changed in > the code. > > The commit below is a prime example of change noise. It touched 6 > files/folders and made 28 line changes, but only 4 lines are actual code > changes. > > If you feel whitespace changes are absolutely necessary, please commit them > in a separate commit that includes nothing but whitespace changes and has a > commit message clearly stating that. > > Thank you. > Joe > >
