[oe] [PATCH 2/2] recipes: Update recipes to get 'bitbake world' parse and calculate runqueue successfully.
Khem Raj
raj.khem at gmail.com
Sat Aug 28 20:38:17 UTC 2010
On Sat, Aug 28, 2010 at 5:40 AM, Frans Meulenbroeks
<fransmeulenbroeks at gmail.com> wrote:
> Koen brought up this in the thread on the review process. As it
> (mostly) is about this thread I felt it was more appropriate here.
>
>
>>> = me
>> = Koen
>
>>> I see two things happening.
>>> - patches are submitted for review but do not gain any feedback in a
>>> reasonable time. I have several patches in the queue that did not get
>>> any feedback.
>>> - people are abusing their powers by rejecting changes without
>>> motivation. See e.g [1] and [2]. I feel if you reject a patch you have
>>> an obligation to explain why you rejected it.
>>
>> If you want to delete a recipe I maintain, the burden is on you or are
>> you saying that maintainers aren't in charge of their recipes anymore?
>
>
>>>[1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-August/023374.html
>>>[2] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-August/023270.html
>
> The 10 recipes Koen nack-ed:
>> recipes/angstrom/angstrom-bootmanager.bb | 2 +-
>> recipes/esc/esc-node-demo_git.bb | 4 +-
>> recipes/meta/meta-toolchain-arago-dvsdk.bb | 1 +
>> recipes/sugar/sugar-fructose.bb | 2 +-
>> recipes/tasks/task-arago-toolchain-target.bb | 3 +-
>> recipes/tasks/task-demo-x11.bb | 17 ++---
>> recipes/tasks/task-gmae.bb | 7 ++
>> recipes/tasks/task-gpe.bb | 6 +-
>> recipes/udev/udev-compat141_141.bb | 6 ++-
>> recipes/vlc/vlc-davinci_0.8.6h.bb | 2 +-
>
> Person: Koen Kooi
> Mail: koen at openembedded.org
> Website: http://dominion.kabel.utwente.nl/koen/cms
> Machines: h2200, ipaq-pxa270, efika, ep93xx, netbook-pro
> Distros: �~Engstr��m
> Interests: OpenSync, GNOME, GPE, Matchbox
> Recipes: abiword, bootchart, dia, farsight, freeciv, fuse, galago,
> geda, gimp,
> Recipes: gnumeric, gobby, obby, imposter, inkscape
> Recipes: *moko*, telepathy, tilibs, xchat, xournal.
>
> I don't know what others think about it, but I see only a few matches.
it really does not matter. This MAINTAINERS file is not defining the boundary
of what people can provide feedback on but its a document which says whom to
approach if a recipe is not being taken care on some issues. There are
many aspects
to patches and all feedback should be welcome.
>
> That of course does not mean that Koen is not entitiled to an opinion.
> Of course not, this is a rerview request and everyone may react to it.
> However, I, and I think most of us would appreciate it if this is done
> in a professional, polite and friendly manner.
> (btw wrt the other two post about the 3 conf/distro/include files I
> proposed to delete: two are gpe, and one is maemo. you may consider
> yourself to be the maintainer of the gpe recipes. I've clearly
> indicated why I wanted to remove them and you did not address any of
> my concerns and observations; also as I wrote before maintainership
> also comes with obligations. These files are clearly broken so it
> seems the maintainer has some work there.)
>
> Frans
>
> PS: I think this is also an excellent case why it is a good idea to
> identify the maintainer within the recipe/
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
More information about the Openembedded-devel
mailing list