From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patchwork Workflow improvement
Date: Sat, 23 Jan 2010 16:12:53 +0100 [thread overview]
Message-ID: <hjf3lk$1oe$1@ger.gmane.org> (raw)
In-Reply-To: <1264258385.21187.29.camel@mattotaupa.wohnung.familie-menzel.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-01-10 15:53, Paul Menzel wrote:
> Dear Holger,
>
>
> Am Samstag, den 23.01.2010, 10:56 +0100 schrieb Holger Hans Peter Freyther:
>> On Saturday 23 January 2010 09:43:24 Holger Hans Peter Freyther wrote:
>
> […]
>
>> I have pushed "holger/staging-branch" to the server. It does contain all
>> patches from patchwork that are still applying. Please go through the branch
>> and cherry-pick or follow up on the emails..
>
> if I understood correctly you mean with »patches from patchwork that are
> still applying« that the mbox file can be applied with `git am` as
> `pw-am.sh` does [1].
>
> That requires that all patches are submitted using `git send-email`,
That is not a hard requirement, but seems to be the most fool-proof one
> Probably every project or developers
> wrote her/his own scripts (as OE did with `pw-am.sh`) and everyone
> reinvents the wheel.
In this case it was purposely reinvented since getting OE developers to
install extra software is like pulling teeth, so a simple shell script
was added.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLWxH0MkyGM64RGpERAgAPAJ0VTGsXK2zviMV5G8Prq/Had2jzEgCfWwxu
u1NK7hM+MNyDm2tDhAFIIug=
=ONPl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-23 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 8:43 Patchwork Workflow improvement Holger Hans Peter Freyther
2010-01-23 9:22 ` Holger Hans Peter Freyther
2010-01-23 9:26 ` Holger Hans Peter Freyther
2010-01-23 9:56 ` Holger Hans Peter Freyther
2010-01-23 14:53 ` Paul Menzel
2010-01-23 15:12 ` Koen Kooi [this message]
2010-01-23 16:46 ` Holger Hans Peter Freyther
2010-01-23 16:53 ` pwclient (was: Patchwork Workflow improvement) Paul Menzel
2010-01-23 21:29 ` pwclient Paul Menzel
2010-01-23 10:42 ` Patchwork Workflow improvement Koen Kooi
2010-01-23 12:19 ` New state for patches not complying with commit policy (was: Patchwork Workflow improvement) Paul Menzel
2010-01-23 14:10 ` New state for patches not complying with commit policy Koen Kooi
2010-01-23 16:11 ` New state for patches not complying with commit policy (was: Patchwork Workflow improvement) Phil Blundell
2010-01-23 18:00 ` New state for patches not complying with commit policy Koen Kooi
2010-01-23 12:56 ` Patchwork Workflow improvement Holger Hans Peter Freyther
2010-01-23 23:40 ` Khem Raj
2010-01-23 23:42 ` Khem Raj
2010-01-24 0:28 ` Rolf Leggewie
2010-01-24 13:00 ` Useful Git hooks for ensuring code quality. (was: Patchwork Workflow improvement) Paul Menzel
2010-01-23 15:19 ` Patchwork Workflow improvement Petr Štetiar
2010-01-23 16:40 ` Holger Hans Peter Freyther
2010-01-23 16:34 ` Rolf Leggewie
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='hjf3lk$1oe$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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.