From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Commit access for SHR guys
Date: Sat, 15 Nov 2008 09:52:59 -0500 [thread overview]
Message-ID: <491EE24B.20809@balister.org> (raw)
In-Reply-To: <200811151244.55149.mickey@vanille-media.de>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Michael 'Mickey' Lauer wrote:
> Am Friday 14 November 2008 14:29:17 schrieb Daniel Willmann:
>> Hi,
>>
>> I want to propose that the SHR guys (Ainulindale, quickdev) get commit
>> access to OE. They already manage their SHR recipes on an overlay here:
>> http://shr.bearstech.com/git/?p=shr-overlay.git;a=summary
>> and it would be nice to get the recipies into OE directly.
>
> +1. It looks like they know what they're doing. Quite a number of platforms
> could benefit from their work on SHR.
What is SHR?
I'm fine with them, provided the commit messages match the OE format :)
Also, do you know if the follow the oe-dev list? I think people with
commit access should at least read the list to understand to group's
thinking as various issues come up.
Philip
>
> Cheers,
>
> :M:
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-11-15 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 13:29 Commit access for SHR guys Daniel Willmann
2008-11-15 11:44 ` Michael 'Mickey' Lauer
2008-11-15 14:52 ` Philip Balister [this message]
2008-11-15 15:30 ` Michael 'Mickey' Lauer
2008-11-19 23:36 ` Michael 'Mickey' Lauer
2008-11-20 7:01 ` Thomas Kunze
2008-11-20 8:11 ` Marcin Juszkiewicz
2008-11-20 12:01 ` Michael 'Mickey' Lauer
2008-11-20 12:36 ` Julien Cassignol
2008-11-20 12:13 ` Rodrigo Vivi
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=491EE24B.20809@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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.