Dear Jon,
in message E1GYBd8-0001Gp-Kd@jdl.com you wrote:
I was wondering if either of these two commands comes close to being a "replacement" for automatically generating the CHANGELOG in a format that is close to what you would like:
Thanks a lot for the suggestions.
If either of these is close, it might be a pretty simple mod to, say, the "git shortlog" script to make it more acceptable.
A variation of (2) is perfectly fine with me:
git log | egrep -v '^Merge'
[I think the commit ID should be included.]
So since I seem to be the only person on this planet who likes to have this CHANGELOG file, and it has caused so much trouble already I suggest the following procedure:
(1) I will freeze the current setup and probably even release it as U-Boot 1.1.5 (mostly to feed all those FTP-only downloaders).
(2) rename CHANGELOG into CHANGELOG.OLD, and start a new CHANGELOG which gets automatically generated using the command above or a variation thereof.
Note: nobody needs to take care of this file. It is purely for my own private needs, and I will manage it on my own. Everybody else can just ignore the existence of this file.
(3) I will merge your and Matthew McClintock's 85xx which (from my point of view) suffer mostly just from the missing CHANGELOG entries.
(4) Remaining issues like coding style cleanup etc. can be then sorted out in the merged trees. If I should see bigger problems I will create branches that can be used as reference.
Is this acceptable to you and everybody else?
Best regards,
Wolfgang Denk