white space unification?

[Ralf Wildenhues]

Do you guys mind if I run libtool.m4 and ltmain.m4sh through `unexpand',
and remove all trailing white space (all branches)?

Furthermore, can I put a rule to this into HACKING, or maybe even have
`commit' do this by itself, if unexpand is available?  (sh.test is fine,
too, if you don't want commit to alter the source).

Rationale: I keep seeing white space diffs when looking at hacked up
libtool variants.  I don't want to see this clutter.  The 4K saving for
libtool.m4 is a nice but largely irrelevant side effect.

On a related note: branch-2-0/HEAD m4 magic to produce all the output
variables leaves quite a number of empty lines in `configure'?  Do you
mind if I create a patch to remove many of them by scattering `dnl' to
some places?

Regards,
Ralf