All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: bp flag added to bug tracker (org.openembedded.stable)
Date: Wed, 07 May 2008 17:53:29 +0200	[thread overview]
Message-ID: <fvsj9q$nk0$1@ger.gmane.org> (raw)
In-Reply-To: <fvseh7$53i$1@ger.gmane.org>

Rolf Leggewie wrote:
> Koen Kooi wrote:

>> If you think you have patches that should get applied to the
>> stablebranch, please post them for review on the stablebranch
>> mailinglist.
>
> Would it be OK if I directed you to http://tinyurl.com/63674m instead?
> Maybe you can save this search in your bugzilla account?  These are
> patches tagged with the bp keyword request.

Navigating bugzilla is sadly on the wrong side of my motivation (read: 
available time) threshold. Why? Because I spend a lot of time offline 
(no access to bugzilla) and I do have a local copy of the stablebranch 
mail folder. I'm sure I can configure bugzilla to mail me and all that, 
but I honestly have no time or inclination to look into that right now.

> The Stable branch devs can
> then ACK or NACK the patch right in the bug tracker.  Second person to
> ACK makes the commit to .stable.  Isn't this the kind of review process
> we are looking for?  Maybe you can over time move the complete review
> process away from the mailing list and into bugzilla.  That would be my
> suggestion.

Moving to bugzilla would be a good thing, but the policy right now works 
for the stable branch maintainers quite well and fits with out 
"lifestyle" (read: available time).

It's nothing against you or bugzilla, just people being (too) busy.

regards,

Koen




  reply	other threads:[~2008-05-07 15:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 14:51 bp flag added to bug tracker (org.openembedded.stable) Rolf Leggewie
2008-05-06 15:24 ` Rolf Leggewie
2008-05-06 17:48   ` Rolf Leggewie
2008-05-06 17:43 ` Koen Kooi
2008-05-06 18:11   ` Graeme Gregory
2008-05-07  9:45   ` Rolf Leggewie
2008-05-07 10:30     ` Koen Kooi
2008-05-07 12:49       ` Rolf Leggewie
2008-05-07 13:35         ` Koen Kooi
2008-05-07 14:32           ` Rolf Leggewie
2008-05-07 15:53             ` Koen Kooi [this message]
2008-05-07 16:41               ` Rolf Leggewie
2008-05-08 10:59                 ` Rolf Leggewie
2008-05-10 12:12                   ` Rolf Leggewie
2008-05-10 12:45                     ` Koen Kooi
2008-05-10 13:45                       ` Rolf Leggewie
2008-05-07 13:37         ` Philip Balister
2008-05-07 14:16           ` Richard Purdie
2008-05-07 15:47             ` Koen Kooi
2008-05-07 16:34               ` Leon Woestenberg
2008-05-07 14:39           ` Rolf Leggewie
2008-05-07 16:18             ` Leon Woestenberg
2008-05-07 17:23               ` Rolf Leggewie
2008-05-07 18:35                 ` Leon Woestenberg
2008-05-07 21:48                 ` Koen Kooi
2008-05-10 23:18           ` Florian Boor
2008-05-11 19:31             ` Leon Woestenberg
2008-05-13 10:46             ` 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='fvsj9q$nk0$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.