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 13:07:59 +0100	[thread overview]
Message-ID: <fpjpiv$7l9$1@ger.gmane.org> (raw)
In-Reply-To: <20080221131810.2f58c40e@widy.localdomain>

I have just added the bb and patch keywords to the keyword list
http://bugs.openembedded.org/editkeywords.cgi

keywords are essentially tags and can help us with the multi-dimension
problems we have.  But then again, unlike meta-bugs they don't have
email notification.  They are a tool for aiding bugzilla search.  AFAIK,
it is possible to restrict power to change those tags to certain groups
of bugzilla users which is something we might want to use (if we had a
triaged keyword, for example.  Thinking about it, I'll add that keyword,
too, for experimenting with it)




  parent reply	other threads:[~2008-02-21 12:08 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
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 [this message]
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='fpjpiv$7l9$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.