From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org,
"Rafał Miłecki" <zajec5@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 0/5] b43: more N-PHY stuff
Date: Fri, 22 Jan 2010 23:33:40 +0100 [thread overview]
Message-ID: <201001222333.42554.mb@bu3sch.de> (raw)
In-Reply-To: <201001222259.28933.mb@bu3sch.de>
On Friday 22 January 2010 22:59:26 Michael Buesch wrote:
> On Friday 22 January 2010 21:47:03 Rafał Miłecki wrote:
> > As you can see I've used git send-email for submission this time! I've
> > no idea what I did wrong that patch 1/5 was sent incorrectly. I just
> > generated patches with
> > git format-patch --cover-letter -o b43
> > , then modified 0000-...patch (ONLY this one) and finally sent all
> > patches from b43 directory.
>
> The mails may be re-encoded on intermediate mailservers.
> My server, for example, re-encodes all of your mails to base64.
> (or it may be the list-mailserver re-encoding the mails, because by server
> doesn't advertise the correct flags, I dunno...)
> I don't know why it does this, however. I'm still pretty sure that it's related
> to the characters in your name. Does anybody has an idea how to fix this? I'm using exim.
>
Oh, I just realize that these patches received via vger.kernel.org list are just fine.
It's just berlios' mailman which mangles the mails for me. Which is not surprising,
because berlios is a really really broken platform and its mailservers are even worse than that.
So I guess everything is fine now.
So while we are at it, I'd really like to migrate away from the berlios list.
It's really just annoying. Does somebody have a good reliable mailinglist service
we could migrate to? Does vger offer lists to driver projects?
--
Greetings, Michael.
next prev parent reply other threads:[~2010-01-22 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 0:53 [PATCH 0/5] b43: more N-PHY stuff Rafał Miłecki
2010-01-22 0:53 ` [PATCH 1/5] b43: check band width Rafał Miłecki
2010-01-22 0:53 ` [PATCH 2/5] b43: N-PHY: implement overriding RF control Rafał Miłecki
2010-01-22 0:53 ` [PATCH 3/5] b43: N-PHY: add running samples Rafał Miłecki
2010-01-22 0:53 ` [PATCH 4/5] b43: N-PHY: add setting power amplifier filters Rafał Miłecki
2010-01-22 0:53 ` [PATCH 5/5] b43: N-PHY: add TX tone Rafał Miłecki
2010-01-22 15:01 ` [PATCH 0/5] b43: more N-PHY stuff Gábor Stefanik
2010-01-22 15:21 ` Larry Finger
2010-01-22 20:47 ` Rafał Miłecki
2010-01-22 21:59 ` Michael Buesch
2010-01-22 22:33 ` Michael Buesch [this message]
2010-01-23 1:16 ` John W. Linville
2010-01-23 3:36 ` David Woodhouse
2010-01-23 11:33 ` Michael Buesch
2010-01-23 15:09 ` Stefano Brivio
2010-01-23 15:28 ` Rafał Miłecki
2010-01-22 21:32 ` John W. Linville
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=201001222333.42554.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@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.