From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patchwork cleanup call
Date: Fri, 22 Oct 2010 10:21:37 +0200 [thread overview]
Message-ID: <i9rhih$lbh$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=-w36_=-iZz7QB6kjgQ8_nUfpyg9Jv3a+iHQVP@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-10-10 09:32, Frans Meulenbroeks wrote:
> As far as I see it there are two often occurring situations:
>
> - a patch is submitted for review and gets zero feedback. I have quite
> a few of these in patchwork. I once proposed that if a patch does not
> get neg feedback in two weeks or so it could be pushed anyway. While
> this got some positive response it was never really made a policy. But
> I must say I'm becoming more and more inclined to push them anyway.
>
> - a patch is submitted by someone without commit access but no one
> picks up the patch.
What I do is ping patches that get zero feedback, people sending patches
should do the same.
And when I'm travelling I can't post to the ml, so every month there's a
working week were I can't give feedback and with my goldfish memory I
forget it the week after.
And if you're going to push an 'old' unreviewed patch, it's easy enough
to ack it on the ml and wait a bit to see if someone suddenly spots a
huge bug in the patch.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMwUmRMkyGM64RGpERAh7mAJ9ZyDnQo45N01fLgaC87u8umFaxfgCdEmr0
UciwwVyzo9CnkokxRpuehxk=
=mbDk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-10-22 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 20:58 patchwork cleanup call Khem Raj
2010-10-22 6:44 ` Koen Kooi
2010-10-22 6:55 ` Martin Jansa
2010-10-22 7:32 ` Frans Meulenbroeks
2010-10-22 8:21 ` Koen Kooi [this message]
2010-10-22 8:43 ` Martin Jansa
2010-10-22 9:15 ` Frans Meulenbroeks
2010-10-22 10:16 ` Koen Kooi
2010-10-22 10:32 ` Frans Meulenbroeks
2010-10-22 12:42 ` Andreas Oberritter
2010-10-22 14:01 ` Frans Meulenbroeks
2010-10-22 15:07 ` Khem Raj
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='i9rhih$lbh$1@dough.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.