I just submitted a linux-yocto-3.0 kernel patchset to linux-yocto and was very unpleasantly surprised to see that the kernel devs mentioned in a resubmitted patch were automatically CC:ed on my Yocto e-mail cover letter as well as for the resubmitted patch: https://lists.yoctoproject.org/pipermail/yocto/2012-July/010060.html
Which command did you use to send the patches? Did you use -a or -c?
-a
OK, so this is working as documented in the help text: -a Send the cover letter to every recipient listed in Cc and Signed-off-by lines found in the cover letter and the patches. This option implies -c. At first I thought this was a repeat of the previous issue where patches being added to a recipe were being parsed and the CCs added - but it doesn't appear to be. The patch itself had these CC lines, so this is working as designed. What behavior did you expect from -a?
Ah, ok, yeah, my mistake, I've just become used to always using -a without thinking about it or reading the help text. Basically send-pull-request should just never be used for linux-yocto kernel patches, period. Now I remember why I used to just do them manually...
(In reply to comment #4) > Ah, ok, yeah, my mistake, I've just become used to always using -a without > thinking about it or reading the help text. > > Basically send-pull-request should just never be used for linux-yocto kernel > patches, period. > > Now I remember why I used to just do them manually... If you don't use -a -c then it will do the right thing and only send to the list specified via the -t on the command line. This is how I do it. Note that git send-email will embarass you in exactly the same way if using a similar option.
setting this to verified