All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bluez4: Added new recipe version 4.96
Date: Fri, 12 Aug 2011 11:29:23 +0100	[thread overview]
Message-ID: <201108121129.23973.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <B10F3DBD-4A1F-45AE-886D-A08FDDA130E8@dominion.thruhere.net>

On Friday 12 August 2011 11:11:24 Koen Kooi wrote:
> On a more serious note, how does one become a maintainer for a recipe in
> OE-core? Bluez4 only seems to get updates when someone tries to update
> recipes-connectivity/* and doesn't seem to get actually used or runtime
> tested.

Surely maintainer or not you can just test and send patches for the BlueZ 
recipe in OE-core as you would any other recipe? I suspect if you do this 
often enough you'll become the de-facto maintainer anyway.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-08-12 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 16:00 [PATCH] bluez4: Added new recipe version 4.96 Noor, Ahsan
2011-08-11 16:02 ` Phil Blundell
2011-08-11 20:26   ` Saul Wold
2011-08-12  7:18     ` Ahsan, Noor
2011-08-12  7:29       ` Martin Jansa
2011-08-12  7:50         ` Ahsan, Noor
2011-08-12  9:10         ` Paul Eggleton
2011-08-12 10:11           ` Koen Kooi
2011-08-12 10:29             ` Paul Eggleton [this message]
2011-08-12 17:28               ` Saul Wold

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=201108121129.23973.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.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.