[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] patchwork service.
From: |
Michael S. Tsirkin |
Subject: |
Re: [Qemu-devel] patchwork service. |
Date: |
Tue, 6 Oct 2009 18:38:45 +0200 |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
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
- Re: [Qemu-devel] patchwork service.,
Michael S. Tsirkin <=