From: Jeremy Kerr <jk@ozlabs.org>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: patchwork@lists.ozlabs.org, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: tracking qemu-devel at patchwork.ozlabs.org
Date: Fri, 31 Jul 2009 10:58:44 +1000 [thread overview]
Message-ID: <200907311058.44607.jk@ozlabs.org> (raw)
In-Reply-To: <4A723E2F.7070504@gmx.net>
Hi Carl-Daniel,
> AFAIK patchwork ignores all mails without Message-ID. That's IMHO a
> feature which other projects (flashrom, coreboot) rely on for their
> patchwork installation because commit mails often don't have such an
> ID and are thus ignored automatically.
Cooler way to get patchwork to ignore a message:
X-Patchwork-Hint: ignore
I use this for "I'm about to send the following patches upstream" mails,
as all of the patches have already been posted to the list.
IIRC, an MTA on the mail's path may assign a Message-Id itself, if the
mail doesn't already have one.
Cheers,
Jeremy
next prev parent reply other threads:[~2009-07-31 1:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 9:04 [Qemu-devel] tracking qemu-devel at patchwork.ozlabs.org Michael S. Tsirkin
2009-07-29 11:08 ` [Qemu-devel] " Jeremy Kerr
2009-07-29 12:25 ` Michael S. Tsirkin
2009-07-29 13:25 ` Anthony Liguori
2009-07-29 22:52 ` Jeremy Kerr
2009-07-30 12:34 ` Michael S. Tsirkin
2009-07-30 23:41 ` Jeremy Kerr
2009-07-31 0:43 ` Carl-Daniel Hailfinger
2009-07-31 0:58 ` Jeremy Kerr [this message]
2009-07-31 13:10 ` Michael S. Tsirkin
2009-08-01 6:15 ` Jeremy Kerr
2009-08-02 6:31 ` Michael S. Tsirkin
2009-08-02 16:40 ` Michael S. Tsirkin
2009-08-03 11:09 ` Michael S. Tsirkin
2009-08-03 11:44 ` Jeremy Kerr
2009-08-03 12:21 ` Michael S. Tsirkin
2012-03-12 20:37 ` [Qemu-devel] " Michael S. Tsirkin
2012-03-13 0:56 ` Jeremy Kerr
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=200907311058.44607.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=aliguori@us.ibm.com \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=mst@redhat.com \
--cc=patchwork@lists.ozlabs.org \
--cc=qemu-devel@nongnu.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).