From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: what is the process for sending patches about eclipse-poky-kepler?
Date: Mon, 14 Jul 2014 10:58:13 +0100 [thread overview]
Message-ID: <53C3A9B5.5000005@communistcode.co.uk> (raw)
In-Reply-To: <87b40d7036f0487e862c6062ff66ee48@BY2PR03MB254.namprd03.prod.outlook.com>
On 14/07/14 04:13, B40290@freescale.com wrote:
> Hello all,
>
> I need to send patches to eclipse-poky-kepler .
> What is the process for sending patches ?
>
>
>
>
> Thanks,
> Chunrong
>
>
If it's poky specific then I would imagine either sending them to Poky
list, or the Yocto list would be most appropriate.
https://www.yoctoproject.org/tools-resources/community/mailing-lists
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
prev parent reply other threads:[~2014-07-14 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 3:13 what is the process for sending patches about eclipse-poky-kepler? B40290
2014-07-14 9:58 ` Jack Mitchell [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=53C3A9B5.5000005@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox