From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patchwork Workflow improvement
Date: Sat, 23 Jan 2010 11:42:56 +0100 [thread overview]
Message-ID: <hjejrf$m65$1@ger.gmane.org> (raw)
In-Reply-To: <201001230943.24210.holger+oe@freyther.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-01-10 09:43, Holger Hans Peter Freyther wrote:
> Hi All,
>
> right now I'm writing a Qt 4.6 based application that might help us a bit with
> the patchwork queue.
>
> The idea of the script is to have two things at the end:
> 1.) a branch with all the patches that applied and that can be published
> 2.) a list of patches that don't apply.
>
>
> What people are supposed to:
>
> 1.) Cherry pick from the branch
> 2.) Send updated patches, close the reports on patchwork...
I think people that apply those patches to oe.dev should fix up the
commit message as well. The stack Khem pushed this week is just awfull.
I guess we should flag patches with bad commit messages as 'rejected' in
pw ASAP. We can weed out most of them by reject anything that lacks a
':' in the subject line.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLWtKwMkyGM64RGpERAgSAAJ4y0iproyWSH/ojheSFN40fdj16NgCfRfj3
rD4D/FAM3X5NeYdEUTRsbDQ=
=4N5e
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-23 10:45 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
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 ` Koen Kooi [this message]
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='hjejrf$m65$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.