In message tnxirw5ybde.fsf@arm.com you wrote:
Scripts like 'git applymbox' or 'stg import --mail' can do this automatically. With StGIT you can even modify the patch multiple times
Yes, I know. And it works fine if the submitted patchs follow th required conventions. But it is no exception here to receive a base64 encoded file "patch.bz2" which turns out to be a bzip2-compressed _tarball_ containing the patch plus eventually other files like the CHANGELOG entry.
As mentioned before: either I have to reject 90...95% of all patches because they cannot be processed automatically, or I have to do this stuff manually.
You have a pre-commit hook in GIT which you can use to automatically append part of the patch description and author to the changelog file
Yes, I know that such options exist, but I have to admit that I did not understand the documentation:
The default pre-commit hook, when enabled, catches introduction of lines with trailing whitespaces and aborts the commit when a such line is found.
?
(like for Linux, you can ask people to have a short description on the first line or two, followed by an empty line and followed by a longer description).
"I can call spirits from the vasty deep." "Why so can I, or so can any man; but will they come when you do call for them?" - Shakespeare, 1 King Henry IV, Act III, Scene I.
I mean: as long as we cannot have people understand the requested CHANGELOG entry format (if they include such an entry at all), what is the chance that they will do what we ask for? :-(
All that matters is how you are used to work, it's pretty hard to change the work-flow after using it for years. Anyway, in case you
Indeed.
want to automate the patch importing, I can help you with some scripts (or StGIT advice).
I will certainly have to look into StGIT again.
Best regards,
Wolfgang Denk