> But could you write the proper ChangeLog entries to explain not only why > the change but also what change is made? See git log and the GNU Coding > Style. The idea is that they help a *lot* when having to dig back what > happened to a given function, to the use of a macro, etc.
Of course, here are the new patches.
