From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org, lynn.lin@avocent.com
Subject: Re: [RFC] rw for Lynn Lin
Date: Sun, 17 May 2009 09:58:19 -0400 [thread overview]
Message-ID: <4A1017FB.2000204@balister.org> (raw)
In-Reply-To: <4A1014BA.50905@nospam.arcornews.de>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
Rolf Leggewie wrote:
> Hi there,
>
> I went through the bugtracker again and there as many open bugs with
> patches as ever :-( One name that I ran across frequently for providing
> many patches was that of Lynn Lin. I wonder if it isn't time to grant
> rw access. Contributions in the bug tracker are at
> http://tinyurl.com/qwd94k
Sadly, lots of us just do not have time to sort through the bug tracker.
Eventually, we need to decide what to do with the bug tracker. I've
almost convinced myself that bug tracking is the job of the distro
maintainers and each distro should develop there own process to collect
user issues.
> Everybody, please go to http://tinyurl.com/pb9ftf from time to time and
> see if there isn't something you want to commit. That search result is
> also linked from http://bugs.openembedded.net -> "Open tickets with
> patches" link
We do seem to do a much better job with patches sent to this list. The
patches are tracked at:
http://patchwork.openembedded.org/project/openembedded/list/
Patches that can be appliaed via git-am will get processed the fastest.
Philip
PS: I know this is getting posted twice ... I am checking the both
lists.oe.org and oe.org and receiving email.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-05-17 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 13:44 [RFC] rw for Lynn Lin Rolf Leggewie
2009-05-17 13:58 ` Philip Balister [this message]
2009-05-17 14:18 ` Phil Blundell
2009-05-21 7:36 ` Stanislav Brabec
2009-05-21 16:08 ` Marcin Juszkiewicz
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=4A1017FB.2000204@balister.org \
--to=philip@balister.org \
--cc=lynn.lin@avocent.com \
--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.