From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2] nettle: The variable named p in the patch file was incorrectly named.
Date: Fri, 11 Mar 2016 10:47:02 +0000 [thread overview]
Message-ID: <1457693222.7305.2.camel@linux.intel.com> (raw)
In-Reply-To: <1457540251-8951-1-git-send-email-nathangutzmann@gmail.com>
On Wed, 2016-03-09 at 09:17 -0700, ngutzmann wrote:
> The variable in question should have been called ecc->p. The patch
> has been updated
> so that the compilation of the nettle recipe would complete
> successfully. The backport
> originated from this commit
> https://git.lysator.liu.se/nettle/nettle/commit/c71d2c9d20eeebb985e38
> 72e4550137209e3ce4d
Thanks a lot for this patch, I've just proposed it for inclusion in the
Fido branch.
I missed this originally because it's not tagged fido, for future it's
worth pointing out that in order to be sure patches for stable branches
are noticed by the maintainers we request the subject is prefixed with
[branchname].
Thanks again for your contribution.
Joshua
prev parent reply other threads:[~2016-03-11 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 16:17 [meta-oe][PATCH v2] nettle: The variable named p in the patch file was incorrectly named ngutzmann
2016-03-11 10:47 ` Joshua G Lock [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=1457693222.7305.2.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox