Re: Run entire codebase through GNU Indent?

One can tag the git commit immediately before the one in which GNU indent
was used and then people can git-blame at that commit if they are
interested in tracking authorship of code changes implemented before that.

The major question here is: what is greater? (A) The benefit of code
readability by having consistent indentation accross the whole codebase or
(B) The git-blame issue?

I'd say B is a tolerable issue given that there is a known workaround (as I
have just described above) and that A seems to be a good thing for the
project in the long term.

Happy hacking,
Felipe Sanches
Em 11/07/2014 13:40, "Behdad Esfahbod" <[email protected]> escreveu:

> PLEASE DON'T.  It will make "git blame" useless.
>
> On 14-07-11 12:33 PM, Dave Crossland wrote:
> >
> > Hi!
> >
> > I started a discussion on Github issue tracker about this:
> >
> > https://github.com/fontforge/fontforge/issues/1502
> >
> > --
> > Cheers
> > Dave
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Fontforge-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/fontforge-devel
> >
>
> --
> behdad
> http://behdad.org/
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fontforge-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-devel
>

------------------------------------------------------------------------------

_______________________________________________
Fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel