From mboxrd@z Thu Jan  1 00:00:00 1970
From: Karl O. Pinc <kop@meme.com>
Date: Fri, 03 Aug 2012 19:56:11 -0500
Subject: [U-Boot] The way the list manages patch submission
In-Reply-To: <20120803224656.21EDF203A89@gemini.denx.de> (from wd@denx.de on
	Fri Aug  3 17:46:56 2012)
Message-ID: <1344041771.12337.2@mofo>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 08/03/2012 05:46:56 PM, Wolfgang Denk wrote:
> I have no diea why there are two people (Karl and Any) appear to have
> problems with list delivery - I cannot see any such problems.  As far
> as I can tell, all their messages have been properly delivered to the
> list and the archives.  I tend to believe these are local problems
> on their own end, but without precise error reports I don;t ieen have
> a clue what to look for.

The trouble is getting a patch message back from the list when you
send a patch in.  For example I sent
<1344017124-5749-1-git-send-email-kop@meme.com>
[PATCH v2] README: Add handy kermit primer
The mail logs show the message going out, but nothing
ever comes back with that message id.
(Of course I don't see the message id if my
system rejects the inbound message, but why
would it reject just my patches from the list?)

Perhaps it's because git send-email automatically cc-s me,
so the list decides not to send the patch back?
I've added myself as a cc to this message to see
if that matters.

In any case it's not a big deal.  It's just, odd.
If you really care you can look at your logs
and watch the above message id come in and
what happens to it.

Regards,

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein