public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@linutronix.de>
To: Erik Mouw <mouw@nl.linux.org>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Andrew Victor <linux@maxim.org.za>,
	Pierre Ossman <drzeus@drzeus.cx>, Eric BENARD <ebenard@free.fr>,
	ARM Linux Mailing List  <linux-arm-kernel@lists.arm.linux.org.uk>,
	"Hans J. Koch" <hjk@linutronix.de>,
	Russell King <rmk@arm.linux.org.uk>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/7] mmc: at91_mci: rework to allow better transfer
Date: Wed, 18 Jun 2008 13:40:57 +0200	[thread overview]
Message-ID: <20080618114057.GE2226@local> (raw)
In-Reply-To: <20080618111607.GB6788@gateway.home>

On Wed, Jun 18, 2008 at 01:16:07PM +0200, Erik Mouw wrote:
> On Wed, Jun 18, 2008 at 12:47:23PM +0200, Erik Mouw wrote:
> > On Wed, Jun 18, 2008 at 12:04:49PM +0200, Nicolas Ferre wrote:
> > 
> > [...]
> > 
> > Could you all drop =?ISO-8859-1?Q?Hans-J=FCrgen_?= from the Cc list in
> > this thread? The address is invalid because it has no domain part and
> > hence causes quite some bounces on the list because some strict email
> > checkers reject invalid addresses in the Cc list.
> > 
> > I'm trying to figure out what went wrong, but in the mean time please
> > drop =?ISO-8859-1?Q?Hans-J=FCrgen_?= from the Cc list.
> 
> Found it, Mailman is to blame. On the linux-kernel mailing list, the
> address shows up ok: "=?ISO-8859-1?Q?Hans-J=FCrgen_?=
> =?ISO-8859-1?Q?Koch?= <hjk@linutronix.de>".
> 
> What probably happens: Mailman tries to check if the addresses in the
> To and CC fields are subscribed to the list (linux-arm-kernel). If that
> is the case and the subscriber enabled "prevent doubles", it won't send
> that particular subscriber the message. Of course, this should have
> been implemented by a simple strncmp() on the To and CC fields, but I
> guess Mailman first breaks up the To and CC fields, then does the
> "prevent double" check, and then reassembles the To and CC fields.
> Apparently there is an error in the break up or reassembly. Now how to
> fix this without breaking Mailman alltogether...
> 
> In the mean time, could you just use Hans-J?rgen's address
> (hjk@linutronix.de>) and not his name in the CC field?

I avoided the German umlaut in my name by using the abbreviation "Hans
J. Koch" on mailing lists. Unfortunately, I still have one mail client
that uses the full name. I'll fix that to avoid similar trouble.

On the other hand, I used that for quite a while now, and didn't have
problems. It shouldn't be too difficult to have these programs use UTF-8
(or any other charset) properly these days.

Thanks,
Hans

> 
> 
> Erik
> [linux-arm-kernel-owner #2]
> (thanks to David Woodhouse for helping to debug the problem)
> 
> -- 
> Erik Mouw -- mouw@nl.linux.org



  reply	other threads:[~2008-06-18 11:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 11:49 [PATCH 0/7] mmc: at91_mci: rework to allow better transfer Nicolas Ferre
2008-05-30 12:18 ` [PATCH 5/7] mmc: at91_mci: update bytes_xfered value once xfer done Nicolas Ferre
2008-06-01 14:44   ` Russell King - ARM Linux
2008-05-30 12:26 ` [PATCH 6/7] mmc: at91_mci: add sdio irq management Nicolas Ferre
2008-05-30 12:28 ` [PATCH 7/7] mmc: at91_mci: do not read irq status twice as it will forget some errors Nicolas Ferre
2008-05-30 12:43 ` [PATCH 1/7] mmc: at91_mci: support for block size not modulo 4 Nicolas Ferre
2008-05-30 12:44 ` [PATCH 2/7] mmc: at91_mci: show timeouts Nicolas Ferre
2008-05-30 12:45 ` [PATCH 3/7] mmc: at91_mci: avoid timeouts Nicolas Ferre
2008-05-30 12:45 ` [PATCH 4/7] mmc: at91_mci: add multiwrite switch Nicolas Ferre
     [not found] ` <483FED84.50100@atmel.com>
2008-05-30 12:57   ` [PATCH 1/7] mmc: at91_mci: support for block size not modulo 4 Marc Pignat
     [not found] ` <483FEE58.5000500@atmel.com>
2008-06-01 14:42   ` [PATCH 4/7] mmc: at91_mci: add multiwrite switch Russell King - ARM Linux
2008-06-09 10:42     ` Pierre Ossman
2008-06-09 13:08       ` Russell King - ARM Linux
2008-06-09 13:42         ` Pierre Ossman
2008-06-09 13:53           ` Russell King - ARM Linux
2008-06-09 13:58             ` Pierre Ossman
2008-06-09 10:46 ` [PATCH 0/7] mmc: at91_mci: rework to allow better transfer Pierre Ossman
2008-06-10  9:54   ` Nicolas Ferre
2008-06-14 16:28     ` Pierre Ossman
2008-06-18 10:04       ` Nicolas Ferre
2008-06-18 10:47         ` Erik Mouw
2008-06-18 11:16           ` Erik Mouw
2008-06-18 11:40             ` Hans J. Koch [this message]
2008-06-18 11:47               ` David Woodhouse
2008-06-18 13:35                 ` Erik Mouw
2008-06-18 13:37                   ` David Woodhouse
2008-06-18 15:17                     ` Erik Mouw
2008-06-20 16:30         ` Pierre Ossman
     [not found]           ` <6306c640806201005n17aba42ag6f0bc344256a1ad@mail.gmail.com>
2008-06-20 17:25             ` Pierre Ossman

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=20080618114057.GE2226@local \
    --to=hjk@linutronix.de \
    --cc=drzeus@drzeus.cx \
    --cc=dwmw2@infradead.org \
    --cc=ebenard@free.fr \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=mouw@nl.linux.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=rmk@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox