From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
froh@novell.com, mailman-owner@linuxfoundation.org,
"Ozan Çağlayan" <ozancag@gmail.com>,
mcgrof@kernel.org, linux-wireless@vger.kernel.org,
lf_driver_backport@lists.linux-foundation.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [Lf_driver_backport] [PATCH] compat: backport ether_addr_equal
Date: Mon, 11 Jun 2012 15:24:35 -0700 [thread overview]
Message-ID: <20120611222435.GN21439@tux> (raw)
In-Reply-To: <4FD66865.7000901@hauke-m.de>
On Mon, Jun 11, 2012 at 11:51:33PM +0200, Hauke Mehrtens wrote:
> On 06/11/2012 08:49 PM, Luis R. Rodriguez wrote:
> > On Wed, May 16, 2012 at 1:46 PM, Johannes Berg
> > <johannes@sipsolutions.net> 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@gmail.com>
> >>> 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.
Thanks Hauke, in the meantime lets ignore the lf_driver_backport list then...
Luis
prev parent reply other threads:[~2012-06-11 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 9:55 [PATCH] compat: backport ether_addr_equal Ozan Çağlayan
2012-05-16 20:17 ` [Lf_driver_backport] " Luis R. Rodriguez
2012-05-16 20:25 ` Luis R. Rodriguez
2012-05-16 20:37 ` Hauke Mehrtens
2012-05-16 20:46 ` Johannes Berg
2012-06-11 18:49 ` Luis R. Rodriguez
2012-06-11 21:51 ` Hauke Mehrtens
2012-06-11 22:24 ` Luis R. Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120611222435.GN21439@tux \
--to=rodrigue@qca.qualcomm.com \
--cc=froh@novell.com \
--cc=hauke@hauke-m.de \
--cc=johannes@sipsolutions.net \
--cc=lf_driver_backport@lists.linux-foundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mailman-owner@linuxfoundation.org \
--cc=mcgrof@frijolero.org \
--cc=mcgrof@kernel.org \
--cc=ozancag@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.