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: Fri, 22 Feb 2008 10:49:46 +0100	[thread overview]
Message-ID: <fpm5ro$6de$1@ger.gmane.org> (raw)
In-Reply-To: <47BE486F.6020604@gmail.com>

Junqian Gordon Xu wrote:
> I got the following message when clicking the link.

http://bugs.openembedded.net/describekeywords.cgi is the correct link.
One gets there by clicking "Keywords:" in any of the bugs for example.

We are just testing this out right now.  But I think it will help us.
Should you require additional keywords just let one of the admins know.

Junqian, can you tell me if you can add or remove a keyword from a bug?




  reply	other threads:[~2008-02-22  9:50 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
2008-02-21 12:57         ` Rolf Leggewie
2008-02-22  3:58         ` Junqian Gordon Xu
2008-02-22  9:49           ` Rolf Leggewie [this message]
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='fpm5ro$6de$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.