All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: bp flag added to bug tracker (org.openembedded.stable)
Date: Sat, 10 May 2008 14:12:52 +0200	[thread overview]
Message-ID: <g043g8$imb$1@ger.gmane.org> (raw)
In-Reply-To: <fvumf4$2te$1@ger.gmane.org>

Rolf Leggewie wrote:
> Rolf Leggewie wrote:
>> Koen Kooi wrote:
>>> 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.
>> Done ;-)
>>
>> For now, I added both oe-stablebranch and you to the list to cc whenever
>> the bp flag is requested.
> 
> It doesn't look like the mails make it to the list.  Can you please
> white-list bugzilla-daemon@amethyst.openembedded.net?
> 
> Koen, do you receive the notification mails?  We have quite a list of
> backport request by now.  Most of them easily applicable.
> 
> http://bugs.openembedded.net/request.cgi?action=queue&requester=&product=&type=all&requestee=&component=&group=type

Are "the stable guys" gonna let them rot in the BTS despite the efforts
I made to accomodate the requests you made?  If you are continuing to
ignore the patches (some of which I prepared just so you would not have
to inspect the changes between .stable and .dev yourselves), I might as
well close them all out as wontfix with a comment that .stable is
unsupported and the people "supporting" it don't care unless you jump
through whatever hoops-of-the-day they present you with.

So much for "same day review".

Last warning to take at least a little care about your .stable bugs and
patches in the tracker or have them all auto-closed.  If .stable chooses
to ignore the BTS we might as well make that transparent and inform the
poor fellows making the reports and hoping for support that they are out
of luck.




  reply	other threads:[~2008-05-10 12:14 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
2008-05-07 16:41               ` Rolf Leggewie
2008-05-08 10:59                 ` Rolf Leggewie
2008-05-10 12:12                   ` Rolf Leggewie [this message]
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='g043g8$imb$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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.