[oe] [RFC] Perfect(?) workflow for patches.
Khem Raj
raj.khem at gmail.com
Sat Jan 30 02:35:10 UTC 2010
there is a script in contrib/patchwork
you can call it
pw-am.sh n1 n2 ....
where n1 n2 are the patch id from patch work.
e.g.
http://patchwork.openembedded.org/patch/1532/
would be
pw-am.sh 1532
On 1/29/10, Frans Meulenbroeks <fransmeulenbroeks at gmail.com> wrote:
> 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?
> I've peeked at pwclient, but ended up with python errors.
>
> FM
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
More information about the Openembedded-devel
mailing list