From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MWgVz-00027w-8n
	for qemu-devel@nongnu.org; Thu, 30 Jul 2009 21:02:31 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MWgVu-0001uj-1L
	for qemu-devel@nongnu.org; Thu, 30 Jul 2009 21:02:30 -0400
Received: from [199.232.76.173] (port=35603 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MWgVt-0001uN-S5
	for qemu-devel@nongnu.org; Thu, 30 Jul 2009 21:02:25 -0400
Received: from bilbo.ozlabs.org ([203.10.76.25]:60385)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jk@bilbo.ozlabs.org>) id 1MWgVt-0002iJ-9l
	for qemu-devel@nongnu.org; Thu, 30 Jul 2009 21:02:25 -0400
From: Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [Qemu-devel] Re: tracking qemu-devel at patchwork.ozlabs.org
Date: Fri, 31 Jul 2009 10:58:44 +1000
References: <20090729090431.GA4438@redhat.com>
	<200907310941.37221.jk@ozlabs.org> <4A723E2F.7070504@gmx.net>
In-Reply-To: <4A723E2F.7070504@gmx.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907311058.44607.jk@ozlabs.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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