Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "André Draszik" <git@andred.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] opkg: backport patch to fix build when sha256 support is enabled
Date: Wed, 13 Jul 2016 13:04:31 +0100	[thread overview]
Message-ID: <1468411471.23527.13.camel@andred.net> (raw)
In-Reply-To: <CAJTo0LZnQXU+uFXxi6pYX6Q9-Xb9hM=VtG8m6PEeUL6QYT2G-Q@mail.gmail.com>

Ross,

On Mi, 2016-07-13 at 11:23 +0100, Burton, Ross wrote:
> On 13 July 2016 at 11:19, André Draszik <git@andred.net> wrote:
> 
> > +++
> > b/meta/recipes-devtools/opkg/opkg/0001-release-fix-implicit-declaration-
> > of-release_get_sha2.patch
> > @@ -0,0 +1,78 @@
> > +From 3fe6c043f5d62710f86ca92692b02f4ffd3bb5c9 Mon Sep 17 00:00:00 2001
> > +From: =?UTF-8?q?Andr=C3=A9=20Draszik?= <ad@andred.net>
> > +Date: Fri, 24 Jun 2016 13:18:52 +0100
> > +Subject: [PATCH] release: fix implicit declaration of
> > release_get_sha256()
> > +MIME-Version: 1.0
> > +Content-Type: text/plain; charset=UTF-8
> > +Content-Transfer-Encoding: 8bit
> > 
> 
> This patch needs an explanation, signed-off-by, and upstream-status.

Explanation and upstream-status are in the commit message of the actual
cherry-picked opkg patch, just not explicitly in the OE commit message.

Do you want me to copy the two into the OE commit message as well?

I've added the Signed-off-by in v2 before I saw your mail.


Cheers,
Andre'



      reply	other threads:[~2016-07-13 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 10:19 [PATCH] opkg: backport patch to fix build when sha256 support is enabled André Draszik
2016-07-13 10:22 ` [PATCH v2] " André Draszik
2016-07-13 10:25   ` Burton, Ross
2016-07-13 10:23 ` [PATCH] " Burton, Ross
2016-07-13 12:04   ` André Draszik [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=1468411471.23527.13.camel@andred.net \
    --to=git@andred.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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