Dear Catalin,
in message tnxbr21v0no.fsf@arm.com you wrote:
A suggestion - since you are using GIT, you could automatically generate the changelog from the patch comments and no longer keep this
I would still need to copy & paste the information from the message, and collect submitter name and date from the mail headers. I think it is impoortant to be able to match a change to the original posting of the submitter on the mailing list.
In this respect, the CHANGELOG entry is a condensed form of the patch comments with additional information about the sugbmitter which I need in any case - no matter if I explicitely register it in a CHANGELOG file or not.
file under revision control. People using GIT would just run gitk or git log to see what has changed. For people using snapshot or releases, you would would put the changelog in the tarball.
Please note that I also continue to keep the CVS server at SF in sync with all development going on on the main branch of the git repository. This is another place where the CHANGELOG file comes in handy.
It's even easier if you only accept patches in text/plain format and use GIT (or other tools on top) to automatically import the patches from the saved e-mail (the author information being automatically preserved).
It would be easier for me, indeed - much easier, as I would have to reject 98% of all submitted patches.
Also, I am strictly against automatically importing unchecked patches. Too many patches contain horrible nonsense and would basicly corrupt the repository. And if I have to process / filter the paches anyway, then it does not make any difference if I run this command or that one.
But thanks for the well-meant suggestion.
Best regards,
Wolfgang Denk