From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39284)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1UXy2q-0003P7-Tj
	for qemu-devel@nongnu.org; Thu, 02 May 2013 14:15:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1UXy2p-0007QD-Eu
	for qemu-devel@nongnu.org; Thu, 02 May 2013 14:15:52 -0400
Received: from mail-vb0-x22e.google.com ([2607:f8b0:400c:c02::22e]:44992)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1UXy2p-0007Q9-7c
	for qemu-devel@nongnu.org; Thu, 02 May 2013 14:15:51 -0400
Received: by mail-vb0-f46.google.com with SMTP id 10so725043vbe.5
	for <qemu-devel@nongnu.org>; Thu, 02 May 2013 11:15:50 -0700 (PDT)
From: Anthony Liguori <anthony@codemonkey.ws>
In-Reply-To: <CAFEAcA_Jm8sgQnNMrrz5H1B1KAgrtiaDm3Br_qbfyFO_D-a+rA@mail.gmail.com>
References: <20130502135143.GA1171@redhat.com>
	<CAFEAcA_Jm8sgQnNMrrz5H1B1KAgrtiaDm3Br_qbfyFO_D-a+rA@mail.gmail.com>
Date: Thu, 02 May 2013 13:15:47 -0500
Message-ID: <87obctp7sc.fsf@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [Qemu-devel] posting patches in pull requests (was Re: [PATCH
	08/29] cpu: Add qemu_for_each_cpu())
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org

Peter Maydell <peter.maydell@linaro.org> writes:

> On 2 May 2013 14:51, Michael S. Tsirkin <mst@redhat.com> wrote:
>> As it is, patchwork is full of patches that were already reviewed and
>> merged, all my scripts that were filtering and sorting patches are also
>> useless, and I get to wade through each patch for the second time.
>
> You need to fix patchwork to have some conception of a
> patch series. Then you can just select the whole series
> which is the pull request and say "ignore this" and you're
> done. Any patch-handling tool that doesn't let you operate
> at the level of a complete series is always going to mean
> you're doing huge amounts of busywork sometimes.

patches solves this problem.  It just requires someone to write a bridge
that updates patchwork based on the information that patches mines.

> I don't particularly object to suggesting that pullreq
> patches are all tagged 'PULL'; I don't think it's very
> likely that you'll get 100% consistency out of everybody
> though.

Ack.

Regards,

Anthony Liguori

>
> -- PMM