From: Ed W <lists@wildgooses.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Bumping ebuilds
Date: Mon, 25 Jul 2011 23:36:28 +0100 [thread overview]
Message-ID: <4E2DEFEC.7000306@wildgooses.com> (raw)
In-Reply-To: <1311505549.23275.52.camel@tablet>
On 24/07/2011 12:05, Peter Volkov wrote:
> В Срд, 13/07/2011 в 11:55 +0100, Ed W пишет:
>> On 07/07/2011 09:30, Dennis.Yxun wrote:
>>> Hi Ed W:
>>> I'm not gentoo dev, and actually not uClibc guy ;-)
>>> But I do suggest you file a bug on http://bugs.gentoo.org
>>> so people who see may help
>>
>> There are lots of open bugs there. The appeal is to find developers who
>> can commit the fixes?
>
> There is possibility to maintain packages via proxy-maintaining[1]. As
> for uClibc I can help you as a proxy, although it'll take some time for
> me to review changes you wish to have in the tree.
>
> [1] http://overlays.gentoo.org/proj/sunrise/wiki/ProxyMaintainer
Sure - I don't really have time to act as a gentoo developer at present,
but that also seems true of a lot of the -embedded dev team. I'm making
a bunch of local ebuilds and it would be useful to feed those upstream
and try and get them into the main tree as quickly as possible.
For sure I can feed bugzilla, but there are plenty of bugs there already
- closing them is the issue, not opening more...
I'm using uclibc, slightly newer than latest release. Actually with
this I see VERY few problems with other ebuilds and my local patch tree
has shrunk to near zero. Pushing that out to tree would be highly
desirable, but I only have x86 to test with - we need some non x86
testers to prove things
Note that uclibc feel that they release infrequently enough that every
release should be considered stable and no one should be lagging the
latest release.
How can we make this happen?
Ed W
prev parent reply other threads:[~2011-07-25 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 7:41 [gentoo-embedded] Bumping ebuilds Ed W
2011-07-07 8:30 ` Dennis.Yxun
2011-07-13 10:55 ` Ed W
2011-07-24 11:05 ` Peter Volkov
2011-07-25 22:36 ` Ed W [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=4E2DEFEC.7000306@wildgooses.com \
--to=lists@wildgooses.com \
--cc=gentoo-embedded@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox