All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: qemu-devel@nongnu.org, Jean-Christophe Dubois <jcd@tribudubois.net>
Subject: Re: [Qemu-devel] patchwork service.
Date: Tue, 6 Oct 2009 18:38:45 +0200	[thread overview]
Message-ID: <20091006163845.GA3548@redhat.com> (raw)
In-Reply-To: <4AAEE220.8040706@gmx.net>

On Tue, Sep 15, 2009 at 02:38:56AM +0200, Carl-Daniel Hailfinger wrote:
> On 15.09.2009 00:50, Anthony Liguori wrote:
> > Jean-Christophe Dubois wrote:
> >> http://patchwork.ozlabs.org/project/qemu-devel/list/
> >>
> >> But it is not used as the patch status is not updated for quite a few
> >> of them (even if they have been accepted/merged since then).  
> >
> > I looked at the patchwork tooling and it didn't seem to easily
> > integrate into my work flow.  It seems to be designed with the idea
> > that you use their tools to pull and manage patches.  I don't think
> > those tools will scale to the volume of patches qemu-devel sees
> > though.  Plus, there's no easy way to deal with the fact that other
> > maintainers may not use it.  Now there are a few thousand patches and
> > trolling through would take ages.
> 
> Note that there are scripts which can be placed in commit hooks and
> automatically mark patches as applied if they were not changed between
> submission and applying.
> There are also scripts which walk the commit history between commit A
> and commit B and run the commit hook script for every commit in between.

Could you post a link to these scripts please?

-- 
MST

  parent reply	other threads:[~2009-10-06 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 21:31 [Qemu-devel] patchwork service Jean-Christophe Dubois
2009-09-14 22:50 ` Anthony Liguori
2009-09-15  0:38   ` Carl-Daniel Hailfinger
2009-09-15  1:38     ` Anthony Liguori
2009-10-06 16:38     ` Michael S. Tsirkin [this message]
2009-10-06 20:54       ` Carl-Daniel Hailfinger
2009-09-15  6:07   ` Jean-Christophe Dubois

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=20091006163845.GA3548@redhat.com \
    --to=mst@redhat.com \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --cc=jcd@tribudubois.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.