All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: [Angstrom-devel] Best place to send new/updated bb files?
Date: Thu, 21 Feb 2008 12:40:48 +0100	[thread overview]
Message-ID: <fpjo00$218$1@ger.gmane.org> (raw)
In-Reply-To: <20080221131810.2f58c40e@widy.localdomain>

Paul Sokolovsky wrote:
>> Simple search shows 50 potential open bugs with new recipes:
>> http://bugs.openembedded.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=attachments.filename&type0-0-0=substring&value0-0-0=.bb

> We even have http://bugs.openembedded.net/show_bug.cgi?id=2194 ,
> maintained by Rolf.

Thanks for bringing that up.  I'd like to see more core devs pay
attention to 2194 which is essentially the bug "I reviewed it, it
contains a patch or request for change in unmistakable terms, but it
touches something I don't understand and might have too far-reaching
implication for me to dare and commit it" - triaged.  IOW, it needs more
experienced people to actually commit or reject the bug.

The bug with the new or updated bb files is 2228, not 2194.




  reply	other threads:[~2008-02-21 11:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fb8538570802200452r5d4360f2ld6330218f4c5c0b6@mail.gmail.com>
     [not found] ` <20080220213121.69007f37@widy.localdomain>
     [not found]   ` <1203591205.6860.103.camel@hammer.suse.cz>
2008-02-21 11:18     ` [Angstrom-devel] Best place to send new/updated bb files? Paul Sokolovsky
2008-02-21 11:40       ` Rolf Leggewie [this message]
2008-02-21 11:48         ` Rolf Leggewie
2008-02-21 12:09           ` Paul Sokolovsky
2008-02-21 12:08         ` Paul Sokolovsky
2008-02-21 12:15           ` Rolf Leggewie
2008-02-21 12:29             ` Paul Sokolovsky
2008-02-21 12:56               ` Rolf Leggewie
2008-02-21 12:07       ` Rolf Leggewie
2008-02-21 12:57         ` Rolf Leggewie
2008-02-22  3:58         ` Junqian Gordon Xu
2008-02-22  9:49           ` Rolf Leggewie
2008-02-28  5:16             ` Junqian Gordon Xu
2008-02-28 10:16               ` 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='fpjo00$218$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.