From: Martin Jansa <martin.jansa@gmail.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 9/9] lttng-ust: 2.6.0 -> 2.6.1
Date: Thu, 28 May 2015 12:03:24 +0200 [thread overview]
Message-ID: <20150528100324.GE2383@jama> (raw)
In-Reply-To: <c2fa9a1b232082e573a4b5e4bb622af5bfe05b62.1432805258.git.liezhi.yang@windriver.com>
On Thu, May 28, 2015 at 02:57:27AM -0700, Robert Yang wrote:
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> .../{lttng-ust_2.6.0.bb => lttng-ust_2.6.1.bb} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename meta/recipes-kernel/lttng/{lttng-ust_2.6.0.bb => lttng-ust_2.6.1.bb} (100%)
>
> diff --git a/meta/recipes-kernel/lttng/lttng-ust_2.6.0.bb b/meta/recipes-kernel/lttng/lttng-ust_2.6.1.bb
> similarity index 100%
> rename from meta/recipes-kernel/lttng/lttng-ust_2.6.0.bb
> rename to meta/recipes-kernel/lttng/lttng-ust_2.6.1.bb
No change in SRCREV? This looks like no-op rename. Please test your
changes.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2015-05-28 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:57 [PATCH 0/9] Packages Upgrade Robert Yang
2015-05-28 9:57 ` [PATCH 1/9] debianutils: 4.4 -> 4.5 Robert Yang
2015-05-28 9:57 ` [PATCH 2/9] git: 2.3.7 -> 2.4.2 Robert Yang
2015-05-28 9:57 ` [PATCH 3/9] python-git: 1.0.0 -> 1.0.1 Robert Yang
2015-05-28 9:57 ` [PATCH 4/9] cracklib: 2.9.3 -> 2.9.4 Robert Yang
2015-05-28 9:57 ` [PATCH 5/9] man-pages: 3.83 -> 4.00 Robert Yang
2015-05-28 9:57 ` [PATCH 6/9] gnupg: 2.1.2 -> 2.1.4 Robert Yang
2015-05-28 9:57 ` [PATCH 7/9] btrfs-tools: 3.18.2 -> 4.0.1 Robert Yang
2015-05-29 13:36 ` Richard Purdie
2015-06-01 2:38 ` Robert Yang
2015-05-28 9:57 ` [PATCH 8/9] nasm: 2.11.06 -> 2.11.08 Robert Yang
2015-05-28 9:57 ` [PATCH 9/9] lttng-ust: 2.6.0 -> 2.6.1 Robert Yang
2015-05-28 10:03 ` Martin Jansa [this message]
2015-05-29 1:31 ` Robert Yang
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=20150528100324.GE2383@jama \
--to=martin.jansa@gmail.com \
--cc=liezhi.yang@windriver.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