On 04/30/2015 10:23 AM, Or Gerlitz wrote: > On 4/30/2015 11:11 AM, Michael Wang wrote: >> On 04/30/2015 09:24 AM, Or Gerlitz wrote: >>> >On 4/30/2015 10:00 AM, Doug Ledford wrote: >>>> >>So, short answer: >>>> >> >>>> >>--cc list options: include all interested parties >>>> >>git log messages: include relevant parties >>> > >>> >makes sense. Michael, please address in your next reposting of the series. >> I'm planning to merge 15~23 into one so the long CC could make more sense. > > I disagree, but let's handle the 1~14 portion of the series 1st (see below) > >> >> And these: >> >> Cc: Hal Rosenstock<hal@xxxxxxxxxxxxxxxxxx> >> Cc: Steve Wise<swise@xxxxxxxxxxxxxxxxxxxxx> >> Cc: Tom Talpey<tom@xxxxxxxxxx> >> Cc: Jason Gunthorpe<jgunthorpe@xxxxxxxxxxxxxxxxxxxx> >> Cc: Doug Ledford<dledford@xxxxxxxxxx> >> Cc: Ira Weiny<ira.weiny@xxxxxxxxx> >> Cc: Sean Hefty<sean.hefty@xxxxxxxxx> >> >> All seems like necessary to be included in the tag list for future trace, could we reserve them in the new 16 patches? > > No, Doug will add his signature as he's the maintainer, so no need to have him twice. The other folks there acted as reviewers on this series and you are not supposed to add the reviewers as Cc to the commits. Just avoid this long listing and put your signature, when people send reviewed-by or acked-by it's handled by patchworks. That's make sense, we can just ask those who participated to provide their reviewed/acked-by instead :-) So I'll reserve 15~23 separately while remove all the cc list, and ask folks to provide their reviewed/acked-by and tested-by in next version. Regards, Michael Wang > > Patch #1 is the actual new enhancement, right? maybe you can have long Cc list there, if you really want. > > Or. > > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
