From: Enrico Joerns <ejo@pengutronix.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/4] Upgrade systemd to 229
Date: Thu, 2 Jun 2016 16:41:58 +0200 [thread overview]
Message-ID: <575045B6.2010200@pengutronix.de> (raw)
In-Reply-To: <1456177012-8588-1-git-send-email-raj.khem@gmail.com>
On 02/22/2016 10:36 PM, Khem Raj wrote:
> diff --git a/meta/recipes-core/systemd/systemd_228.bb b/meta/recipes-core/systemd/systemd_229.bb
> similarity index 93%
> rename from meta/recipes-core/systemd/systemd_228.bb
> rename to meta/recipes-core/systemd/systemd_229.bb
> index b160816..16af0ac 100644
> --- a/meta/recipes-core/systemd/systemd_228.bb
> +++ b/meta/recipes-core/systemd/systemd_229.bb
> @@ -24,35 +24,40 @@ SECTION = "base/shell"
>
> inherit useradd pkgconfig autotools perlnative update-rc.d update-alternatives qemu systemd ptest gettext bash-completion
>
> -SRCREV = "dd050decb6ad131ebdeabb71c4f9ecb4733269c0"
> +SRCREV = "714c62b46379abb7558c544665522aca91691e10"
>
> -PV = "228+git${SRCPV}"
> +PV = "229+git${SRCPV}"
While checking systemd version for trying to update to 230 here, I
discovered that your SRCREV does not match the v229 tag! It is a bunch
of commits past v229 (unlike, for example the 228 SRCREV which did
exactly match the v228 tag.).
Was that done on purpose?
Regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2016-06-02 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 21:36 [PATCH V2 1/4] Upgrade systemd to 229 Khem Raj
2016-06-02 14:41 ` Enrico Joerns [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=575045B6.2010200@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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