From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: Adding Components to Bugzilla
Date: Sat, 08 Dec 2007 14:50:10 +0100 [thread overview]
Message-ID: <475AA112.1020406@student.utwente.nl> (raw)
In-Reply-To: <1281900637.20071208003415@vanille-media.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael 'Mickey' Lauer schreef:
> Koen Kooi wrote:
>> Michael 'Mickey' Lauer schreef:
>>> Hi,
>>>
>>> what would you think about adding (a handful of) components to areas
>>> that are voluntarily maintained in OpenEmbedded? I.e. I'd like to add components
>>> named EFL and Python and make myself the default owner of that
>>> component.
>>>
>>> This could improve structure and responsiveness to bugs.
>
>> On the other hand it decreases it if you get swamped with work, like you
>> were the past year. So, can the oe-issues mailinstlist still get its
>> usual buglog on those bugs?
>
> I think we can hack bugzilla to do that, yeah.
Could you teach sepukku.bbclass about those things as well?
regards,
Koen
- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHWqESMkyGM64RGpERAsk2AJsEi0HJ2vsAPvr4vD3tn0NqQ0okkQCgpRyX
ANwA2xAYy9xHpLJ8jJIne64=
=m/ch
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-12-08 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 20:32 RFC: Adding Components to Bugzilla Michael 'Mickey' Lauer
2007-12-07 21:40 ` Koen Kooi
2007-12-07 23:34 ` Michael 'Mickey' Lauer
2007-12-08 13:50 ` Koen Kooi [this message]
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=475AA112.1020406@student.utwente.nl \
--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.