On 06/11/2012 08:49 PM, Luis R. Rodriguez wrote: > On Wed, May 16, 2012 at 1:46 PM, Johannes Berg > <johannes@xxxxxxxxxxxxxxxx> wrote: >> On Wed, 2012-05-16 at 22:37 +0200, Hauke Mehrtens wrote: >> >>>> Content-Type: text/plain; charset="utf-8" >>>> Content-Transfer-Encoding: base64 >>>> >>>> And then all I see is this when I save the e-mail to a txt file, given >>>> that the encoding is base64. This is odd given that I see you sent >>>> this with X-Mailer: git-send-email 1.7.10.1 -- so not sure how this >>>> ended up going out like this. >>> >>> That's strange, when I save this mail I got over the mailing list with >>> Thunderbird it is not based64 encoded and when looking into the source >>> code with my mail program it is normal text mail. >>> >>> From: =?UTF-8?q?Ozan=20=C3=87a=C4=9Flayan?= <ozancag@xxxxxxxxx> >>> Subject: [PATCH] compat: backport ether_addr_equal >>> Content-Type: text/plain; charset=UTF-8 >>> Content-Transfer-Encoding: 8bit >> >> Well, which list? :-) >> >> I suspect you looked at linux-wireless, and Luis looked at >> lf_driver_backport (given his reply tag), so maybe the >> lf_driver_backport list re-encoded the email. > > Great, so gmail doesn't even let me "see" the linux-wireless e-mail if > it was sent also to lf_driver_backport, I can tell given that I cannot > see the bottom of the e-mail a footer indicating this came from > linux-wireless. If lf_driver_backport re-encoded it then it seems all > patches sent to that list get busted. Bleh. I gotta address this... > > froh you seem to be listed as the owner of the list, can you review this? > > Luis All the mails I got through lf_driver_backport are base64 encoded and if I and the lf_driver_backport mailing list are in CC or TO I just get one mail directly and no mail through the list, different to wireless-testing mailing list where I would get two mails, one directly and one through the list. Hauke -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
