uncrustify

Daniel Poirot dtpoirot at gmail.com
Thu Jan 5 19:18:50 UTC 2017


Before long, everyone will be using a virtual machine with an
integrated editor and common development system!

...oh, wait, that's what started all this:
    https://en.wikipedia.org/wiki/Lisp_machine



On Thu, Jan 5, 2017 at 12:54 PM, Eric S. Raymond <esr at thyrsus.com> wrote:
> Hal Murray <hmurray at megapathdsl.net>:
>>
>> >> Running  uncrustify against NTPsec is good idea, but it needs to
>> >> be a flag day, because it will be a huge patch.
>>
>> > ...pretty much a 'fork' from which there is no recovery...
>>
>> Is that a serious problem?  If so, why?
>>
>> It would mean that I couldn't (usefully) diff versions of a file that crossed
>> the flag day, but I don't think I do that very often.  I'm more likely to let
>> git diff version X and X-1 and if we trust uncrustify I won't be doing that
>> for X being the flag day.
>
> I concur with Hal's doubt that this is a serious problem.  I don't find myself
> doing diffs with very old versions often.  If I did, diff -b (ignoring
> whitespace) would probably mitigate a lot of them.
>
> I've installed uncrustify.  I'll do some experoments.
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


More information about the devel mailing list