Hi Puneeth, Puneeth Chaganti <puncha...@gmail.com> writes:
> But, it looks like the commit message doesn't get into patchwork or is > it that Bastien changed my bad commit message? My commit message also > mentioned that src code blocks don't work, and it possibly because of > new lines being inserted. Your commit message went to the patchwork and I cleaned it up, yes. > Bastien, did you remove it because it was irrelevant? I probably should have kept this information, sorry. I prefered to have a commit message saying what the commit does and not what it does not -- thinking another commit will come soon and complete it. > If the commit message was changed because, Bastien didn't notice it, > can someone tell me the right way to send patches? I noticed it, don't worry :) > I just want to reduce Bastien's trouble and this is leading to > duplication of work, as well. Thanks a lot for that -- the best way to send patches/commits to the list is by using the command "git send-email". Otherwise, the message of the email is taken as the commit message by patchwork, and that I need to reedit a bit. But any other way is okay too, as long as I have the information. Best, -- Bastien
