From: Saul Wold <sgw@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: yoctoproject patches (prelink)
Date: Wed, 02 Jan 2013 10:10:02 -0800 [thread overview]
Message-ID: <50E477FA.8050804@linux.intel.com> (raw)
In-Reply-To: <CAF6bG8enFZOa3A=S-4KLowpCZyed_iD6D-GYFvExWvvyzWFENQ@mail.gmail.com>
On 01/02/2013 05:18 AM, Marko Lindqvist wrote:
> Where and how should patches for git.yoctoproject.org projects be
> submitted? I'm working on patch to make prelink to build with
> automake-1.13. For testing I'm applying it in recipe, but obviously it
> should go in to upstream.
>
Patches should be sent to yocto@yoctoproject.org, also include Mark
Hatle (mark.hatle@windriver.com) as he is one of the Maintainers.
Thanks for working on this.
Sau!
>
> - ML
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2013-01-02 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 13:18 yoctoproject patches (prelink) Marko Lindqvist
2013-01-02 18:10 ` Saul Wold [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=50E477FA.8050804@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cazfi74@gmail.com \
--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.