From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: my IXP4xx patch queue
Date: Wed, 18 Nov 2009 17:51:55 +0100 [thread overview]
Message-ID: <m3hbsru66s.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20091118102916.GC30544@pengutronix.de> ("Uwe Kleine-König"'s message of "Wed, 18 Nov 2009 11:29:16 +0100")
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> writes:
>> I'll git-send-email the latest stuff now. No In-Reply-To:/References
>> since I think the mailserver will hold/drop any mail lacking "Re: "
>> with these headers.
> AFAIK this is not true if your headers match
> /^X-Mailer: git-send-email/ .
>
> My last series took 13 minutes on infradead.org machines and I didn't
> get any bounces about being moderated and the mails don't have headers
> suggesting that they were manually accepted.
Ahh, I didn't know about that, thanks for info.
--
Krzysztof Halasa
prev parent reply other threads:[~2009-11-18 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 21:03 my IXP4xx patch queue Krzysztof Halasa
2009-11-18 10:29 ` Uwe Kleine-König
2009-11-18 16:51 ` Krzysztof Halasa [this message]
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=m3hbsru66s.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).