Am 18.02.2012 10:13, schrieb Blue Swirl: > One way to handle this is gradual reformatting, every time when code > is touched, only changes towards common CODING_STYLE are allowed.
That's what we've been doing wrt braces and I appreciate us not cluttering the history with reformatting commits. Especially at a time where I'm touching every target (and seeing quite some variations on coding style) I'm not so happy about this initiative. > On Fri, Feb 17, 2012 at 15:26, Anthony Liguori <aligu...@us.ibm.com> wrote: >> I don't even want to consider something that touches every line of code. >> That's effectively creating a new source tree and losing the continuity of >> our SCM history. > > I think only 'git blame' output would be affected and that is not 100% > reliable anyway, considering for example code movement. I use repo.or.cz's blame function quite often to find out who to cc or what commit to mention, and (valid) typo fixes are already troublesome, requiring to go to the parent commit and to navigate to the same file in its tree. One cannot specify any custom ignore options there. Is there a better tool to do such interactive, recursive git-blame? Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
