Dear Karl,
In message 1344041771.12337.2@mofo you wrote:
The trouble is getting a patch message back from the list when you send a patch in. For example I sent
Why would you want to get your own messages back? You already know what you sent, don't you?
1344017124-5749-1-git-send-email-kop@meme.com [PATCH v2] README: Add handy kermit primer
Yes, and as you can see for example from the list archive at gmane that has been properly deliverd; also your V2 of it:
08/03 "Karl O. Pinc" [U-Boot] [PATCH] README: Add handy kermit primer http://article.gmane.org/gmane.comp.boot-loaders.u-boot/136913
08/03 "Karl O. Pinc" [U-Boot] [PATCH v2] README: Add handy kermit primer http://article.gmane.org/gmane.comp.boot-loaders.u-boot/136919
The mail logs show the message going out, but nothing ever comes back with that message id.
Why should it?
Perhaps it's because git send-email automatically cc-s me, so the list decides not to send the patch back? I've added myself as a cc to this message to see if that matters.
Your registration in the mailing list has the "nodupes" flag set, which is documented as:
Avoid duplicate copies of messages?
When you are listed explicitly in the To: or Cc: headers of a list message, you can opt to not receive another copy from the mailing list. Select Yes to avoid receiving copies from the mailing list; select No to receive copies.
If the list has member personalized messages enabled, and you elect to receive copies, every copy will have a X-Mailman-Copy: yes header added to it.
You selected that you don't want dupes, so you should not complain that you don't get dupes.
In any case it's not a big deal. It's just, odd.
It is the configuration you selected. If you don't like it, then go to the list page, click on "edit options", and change your settings. Most people prefer it tis way, though.
Best regards,
Wolfgang Denk