From: Adrian Bunk <bunk@stusta.de>
To: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] libxcrypt:upgrade 4.4.6 -> 4.4.7
Date: Tue, 27 Aug 2019 16:21:05 +0300 [thread overview]
Message-ID: <20190827132105.GA17139@localhost> (raw)
In-Reply-To: <20190826053238.28912-1-zangrc.fnst@cn.fujitsu.com>
On Mon, Aug 26, 2019 at 01:32:38PM +0800, Zang Ruochen wrote:
> -License-Update: Many individual files are under other licenses,update their information.
>
> Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
> ---
> .../libxcrypt/{libxcrypt_4.4.6.bb => libxcrypt_4.4.7.bb} | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-core/libxcrypt/{libxcrypt_4.4.6.bb => libxcrypt_4.4.7.bb} (86%)
>...
You also have to rename libxcrypt-compat_4.4.6.bb
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-08-27 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 5:32 [PATCHv2] libxcrypt:upgrade 4.4.6 -> 4.4.7 Zang Ruochen
2019-08-27 13:21 ` Adrian Bunk [this message]
2019-08-27 14:18 ` Richard Purdie
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=20190827132105.GA17139@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=zangrc.fnst@cn.fujitsu.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 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.