> From: Vladimir Sitnikov [mailto:[email protected]]
> Sent: Monday, February 13, 2017 4:00 AM
> To: [email protected]
> Subject: Re: Code Style Guidelines
>
>> My experience is that code reformatting makes history browsing very much
>> harder.
>
> Could you give any example here? What particular use case breaks with
> single-commit reformatting?
It kind of ruins git-blame output and tends to make understanding the scope
of work in any file or tree very unclear.
I recently wanted to see when and why a specific function was added to a
project and ran afoul of exactly this issue: between two moves and a
reformat, the task went from trivial to annoying very fast.
Cheers,
Wyatt
Confidentiality Notice: This electronic message transmission, including any
attachment(s), may contain confidential, proprietary, or privileged information
from Chemical Abstracts Service ("CAS"), a division of the American Chemical
Society ("ACS"). If you have received this transmission in error, be advised
that any disclosure, copying, distribution, or use of the contents of this
information is strictly prohibited. Please destroy all copies of the message
and contact the sender immediately by either replying to this message or
calling 614-447-3600.
