[oe] Tools for Patchwork: `pw-am.sh` and `pwclient` (was: [RFC] Perfect(?) workflow for patches.)

[Paul Menzel]

Am Freitag, den 29.01.2010, 22:57 +0100 schrieb Frans Meulenbroeks:
> 2010/1/24 Paul Menzel <paulepanter at users.sourceforge.net>:
> ?
> >
> > 4. Commit (if not go to 5.)
> >  a) If the reviewer has commit access and accepts the patch, s/he can
> > push it. A hook then changes the Patchwork state to »Applied« with the
> > appropriate commit id and archived(?).
> 
> What is the best way to commit a patch from patchwork?

If the patch is inlined, i. e. you can use the mbox-message for `git
am`, then you can use `contrib/patchwork/pw-am.sh` to get the mbox-file
from Patchwork and it is automatically committed using `git am`.

If the patch has a different format, you can also use the links in the
web interface or `pwclient get`.

> I've peeked at pwclient, but ended up with python errors.

Do you have the latest revision? There were some UTF-8 related problems.
Can you post your errors?


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20100129/510f1dda/attachment-0002.sig>