From: Karl O. Pinc <kop@meme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] The way the list manages patch submission
Date: Fri, 03 Aug 2012 19:56:11 -0500 [thread overview]
Message-ID: <1344041771.12337.2@mofo> (raw)
In-Reply-To: <20120803224656.21EDF203A89@gemini.denx.de> (from wd@denx.de on Fri Aug 3 17:46:56 2012)
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
next prev parent reply other threads:[~2012-08-04 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 18:26 [U-Boot] The way the list manages patch submission Karl O. Pinc
2012-08-03 20:43 ` Andy Sharp
2012-08-03 21:12 ` Karl O. Pinc
2012-08-03 21:45 ` Graeme Russ
2012-08-03 22:46 ` Wolfgang Denk
2012-08-04 0:56 ` Karl O. Pinc [this message]
2012-08-04 13:35 ` Wolfgang Denk
2012-08-04 16:55 ` Karl O. Pinc
2012-08-04 23:08 ` Wolfgang Denk
2012-08-05 9:15 ` Alexander Holler
2012-08-04 16:58 ` Karl O. Pinc
2012-08-04 17:00 ` Karl O. Pinc
-- strict thread matches above, loose matches on Subject: below --
2012-08-04 13:37 Wolfgang Denk
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=1344041771.12337.2@mofo \
--to=kop@meme.com \
--cc=u-boot@lists.denx.de \
/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