Etienne Folio <etienne.folio(a)lrde.epita.fr> writes: Sorry, but that's no excuse. You really didn't know how to describe what your patch does? Then what's the point in committing? How will someone else be able to utilize your work if you do not explain your changes? No, and that's not the problem. Patches must be sent to the list, whatever the method (even manually if needed). Tools are great, but their behavior is *not* the rule: if they have flaws, you should work around them. We are interested in the results, not the means you used. People used to send patches by hand before; tools admittedly simplified the process, but at the same time they have started to give a wrong feeling of safety. Hence the recurring unchecked and ugly ChangeLog entries, missing messages, etc. Committing is not just about saving your changes on a remote/shared machine. It's about sharing useful and reusable work. I know Théo sometimes urge students to commit, but please everybody, take five minutes to clean up your patches before sending them. Thank you in advance.