From: Peter Urbanec <openembedded-devel@urbanec.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Fix for gcc bug 61144
Date: Mon, 13 Oct 2014 14:00:06 +1100 [thread overview]
Message-ID: <543B4036.7040606@urbanec.net> (raw)
In-Reply-To: <1413011133.7562.5.camel@ted>
On 11/10/14 18:05, Richard Purdie wrote:
> On Fri, 2014-10-10 at 10:49 -0700, Saul Wold wrote:
>> Thank you for the patches.
>>
>> Please review the
>> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>
> Just to be clear, because of the important nature of the gcc fix and our
> looming release deadlines, Saul has sent out a version of it in this
> case. We don't normally do that.
Gentlemen,
Thanks for cleaning up the gcc patch and getting it in. Much appreciated!
As far as the pre/postrm patch is concerned, I'll resubmit a little
later. Now that I have some feedback on the patch, I can see scope for
improvement. When I do re-submit, I'll heed the guidelines.
Thanks for your guidance.
Peter
next prev parent reply other threads:[~2014-10-13 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:40 [PATCH] Fix for gcc bug 61144 Peter Urbanec
2014-10-10 17:49 ` Saul Wold
2014-10-11 7:05 ` Richard Purdie
2014-10-13 3:00 ` Peter Urbanec [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-09 13:12 Peter Urbanec
2014-10-10 10:43 ` Martin Jansa
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=543B4036.7040606@urbanec.net \
--to=openembedded-devel@urbanec.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.