> > Hi Vicentiu, Hey Michal > Once a while I browse through the patches in various mailing lists to keep myself informed. > So I came across your patch set pretty randomly. > > I have few tips for you to make your life easier before you get to some serious troubles > with the maintainers ;) > Thanks for the advice. Annoying the maintainers was definitely not my intention. My apologies for any inconvenience. > 1. Always send all the patches in the series to the same recipients list. > > That is, do not send dt-bindings to just Rob, Krzysztof etc. and LED driver > patches to Lee et al. We all need to see the whole thing. > > If you run the scripts/get_maintainer.pl script on the series, you get a complete list. > This is what Krzysztof requested you to do in his comments to v3. Ok. Understood > 2. Use git format-patch and git send-email tools to submit patches. > > If you use these tools you will avoid issues with wrong threading of the messages. > I have a Macbook as a work computer. I've found online that the way to send it on Mac is with mutt. Most certanly I lack some skills, but I took me almost 1 day to have everything working mutt + google account + script mutt_oauth2.py So, quickly jumping to git format-patch and git send-email was something I was not looking forward to. > 3. The following text should not be here. > > You are supposed to just reply in-place to the review messages to acknowledge > that you read the comments and you understand what the reviewers want to > change. Then you send a next version of the series as a new message to all > the recipients. Definitely not as a in-reply-to to the previous version. > Ok. I think I got. Hopefully the next ones will be ok. > > Best regards, > Michal Thanks again and best regards, Vicentiu
