Hey, My git-fu is not absolute, but it sounds like a possible approach. Ideally add a check style target which decides whether the patch is whitespace only and forces the update or even does it automatically.
I doubt there is an easy way to do major refactoring without it not being painful while doing it per partes. Maybe one huge reformat would be much less painful and burdening. I share Matt’s POV on this and have a same hard time understanding the motivation for this change. Regards, Klement > On 9 Apr 2026, at 18:56, Jerome Tollet via lists.fd.io > <[email protected]> wrote: > > > Hi Klement, > Thanks for the suggestion. Would it make sense to add a > .git-blame-ignore-revs file to the repo root for this purpose? It would allow > git blame to automatically skip formatting-only commits when configured with > blame.ignoreRevsFile. > The approach would be: > - Add .git-blame-ignore-revs to the repo (as part of 45485 or a separate > patch) > - After each formatting commit is merged, add its final hash to the file > > TBH, this is a bit painful... > > Jerome > > De : [email protected] <[email protected]> de la part de Klement Sekera > via lists.fd.io <[email protected]> > Date : jeudi, 9 avril 2026 à 18:48 > À : [email protected] <[email protected]> > Objet : Re: [vpp-dev] Side effect of clang-format 'ColumnLimit: 100' > > Hi, > > such patches should also be marked as ignored by git for history examination > tools (like blame). Otherwise it's a huge PITA finding when and why stuff > happened. > > Thanks, > Klement > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26944): https://lists.fd.io/g/vpp-dev/message/26944 Mute This Topic: https://lists.fd.io/mt/118744922/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
