[Qemu-devel] patchwork service.

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Wed Oct 7 07:54:23 EST 2009

[Adding the patchwork mailing list to CC:]

On 06.10.2009 18:38, Michael S. Tsirkin wrote:
> 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?

The scripts I saw were git-based, but I can't remember where I found
them. Maybe someone on the patchwork list knows.

I have attached my personal script which is centered around flashrom and
its svn repo.
Please note that the two svn invocations are intentional. The first one
retrieves a patch designed to be applied with patch -p0, the second one
retrieves the same patch, but from a higher directory so you have to
apply with -p1. AFAIK patchwork generates a hash which normalizes the
first component of the path if it is a directory, so the hash will be
identical for manual diffs from a level above the base directory and git
diffs, but manual diffs inside the base directory will have a different
hash. Generating both styles of patches from the repo increases matching
You will have to change the lines which calculate hashcand to retrieve
the patches from git instead.
The script expects a correct ~/.pwclientrc with your password.

For flashrom, I just run
# update-patchwork 743
if I want to mark revision 743 as committed. You can look at the
corresponding patchwork page here:
http://patchwork.coreboot.org/patch/323/ . Note "State Accepted" and
"Commit r743" at the beginning of the page.



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: update-patchwork
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20091006/13e2340a/attachment.asc>

More information about the Patchwork mailing list