From: Sam Vilain <sam@vilain.net>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vger ate my patch!
Date: Thu, 23 Mar 2006 15:18:02 +1200 [thread overview]
Message-ID: <4422136A.9030604@vilain.net> (raw)
In-Reply-To: <20060322115041.GB21614@mea-ext.zmailer.org>
Matti Aarnio wrote:
>>And if my theory is correct, this message will also not make it to LKML.
>>
>>
>Hmm.. Yes it did... I found them in junk-pile, and the reason was:
>
>
Thanks for that diagnostic, Matti. I had considered that the reason
might have been something to do with the recipients, but thought that a
binary search involving them would have been a tad rude.
>Your MUA software doesn't do proper text element quoting, when said
>element has RFC-822 specials in it.
>
>
Yes, I was hand editing the mbox file produced by `stg mail'. That'll
learn me :-)
Sam.
next prev parent reply other threads:[~2006-03-23 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 4:13 vger ate my patch! Sam Vilain
2006-03-22 11:50 ` Matti Aarnio
2006-03-23 3:18 ` Sam Vilain [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 4:15 Sam Vilain
2006-03-22 6:19 ` Gene Heskett
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=4422136A.9030604@vilain.net \
--to=sam@vilain.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
/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