All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: <yan-liu@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH v1] ltp-ddt: Update to latest
Date: Tue, 24 Apr 2018 12:55:34 -0400	[thread overview]
Message-ID: <20180424165534.GF15846@edge> (raw)
In-Reply-To: <1524507176-14297-1-git-send-email-yan-liu@ti.com>

Is it a duplicate of the same one from yesterday?


On Mon, Apr 23, 2018 at 02:12:56PM -0400, yan-liu@ti.com wrote:
> From: Yan Liu <yan-liu@ti.com>
> 
> Signed-off-by: Yan Liu <yan-liu@ti.com>
> ---
>  .../recipes-devtools/ltp-ddt/ltp-ddt_20180118.bb   |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20180118.bb b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20180118.bb
> index f506c91..1517d17 100644
> --- a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20180118.bb
> +++ b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20180118.bb
> @@ -4,7 +4,7 @@ SECTION = "console/utils"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
> -PR = "r3"
> +PR = "r4"
>  PV_append = "+git${SRCPV}"
>  
>  PROVIDES += "ltp"
> @@ -39,7 +39,7 @@ RDEPENDS_${PN} = "\
>  
>  inherit autotools-brokensep
>  
> -SRCREV = "5b4a12d2d372262cf1184a11340c0ee4f8e93f46"
> +SRCREV = "e2f4f79f1707b63586157801f63050d8f8479b67"
>  BRANCH ?= "master"
>  
>  SRC_URI = "git://arago-project.org/git/projects/test-automation/ltp-ddt.git;branch=${BRANCH} \
> -- 
> 1.7.9.5
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2018-04-24 16:55 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 18:12 [PATCH v1] ltp-ddt: Update to latest yan-liu
2018-04-24 16:55 ` Denys Dmytriyenko [this message]
2018-04-24 17:03   ` Liu, Yan
  -- strict thread matches above, loose matches on Subject: below --
2020-06-03 16:12 yan-liu
2020-05-29 18:29 yan-liu
2020-05-20 19:55 yan-liu
2020-05-13  1:35 yan-liu
2020-05-06 21:37 yan-liu
2020-03-17 15:01 yan-liu
2020-03-04 19:26 yan-liu
2020-02-17 15:05 yan-liu
2020-01-29 15:54 yan-liu
2020-01-23 17:08 yan-liu
2020-01-09 20:48 yan-liu
2020-01-02 20:19 yan-liu
2019-12-11 20:42 yan-liu
2019-11-22 14:22 yan-liu
2019-11-20 19:32 yan-liu
2019-11-13 13:51 yan-liu
2019-10-31 22:07 yan-liu
2019-10-09 20:24 yan-liu
2019-10-02 18:35 yan-liu
2019-09-24 13:48 yan-liu
2019-09-17 20:00 yan-liu
2019-08-19 18:09 yan-liu
2019-08-13 19:19 yan-liu
2019-08-06 20:08 yan-liu
2019-08-07  1:13 ` Denys Dmytriyenko
2019-08-07  2:33   ` Liu, Yan
2019-07-16 15:29 yan-liu
2019-07-09 20:50 yan-liu
2019-07-02 18:19 yan-liu
2019-06-26 17:57 yan-liu
2019-05-21 20:21 yan-liu
2019-03-27 16:55 yan-liu
2019-03-20 18:06 yan-liu
2019-03-05 20:01 yan-liu
2019-03-05 20:20 ` Denys Dmytriyenko
2018-11-14 19:32 yan-liu
2018-11-01 18:43 yan-liu
2018-10-25 12:34 yan-liu
2018-10-08 16:08 yan-liu
2018-09-28 21:30 yan-liu
2018-09-21 21:45 yan-liu
2018-09-14 20:03 yan-liu
2018-08-26 14:55 yan-liu
2018-08-15 16:35 yan-liu
2018-08-02 14:10 yan-liu
2018-07-10 12:44 yan-liu
2018-06-28 14:39 yan-liu
2018-06-18 20:55 yan-liu
2018-05-15 16:05 yan-liu
2018-05-08 17:59 yan-liu
2018-04-30 17:57 yan-liu
2018-04-23 18:19 yan-liu
2018-04-04 14:28 yan-liu
2018-03-27 14:06 yan-liu
2018-03-13 14:12 yan-liu
2017-12-14 13:33 yan-liu
2017-12-05 17:41 yan-liu
2017-11-27 23:06 yan-liu
2017-11-27 23:02 yan-liu
2017-11-27 23:11 ` Liu, Yan
2017-11-20 19:37 yan-liu
2017-11-20 15:26 yan-liu
2017-10-30 21:18 yan-liu
2017-10-24 15:19 yan-liu
2017-10-17 18:00 yan-liu
2017-10-09 17:39 yan-liu
2017-09-18 16:34 yan-liu
2017-09-12 17:53 yan-liu
2017-09-05 15:30 yan-liu
2017-08-28 18:31 yan-liu
2017-08-09 12:10 yan-liu
2017-07-31 15:49 yan-liu
2017-06-19 18:38 yan-liu
2017-06-12 21:31 yan-liu
2017-06-12 16:28 yan-liu
2017-06-05 13:38 yan-liu
2017-05-16 14:13 yan-liu
2017-04-24 13:26 yan-liu
2017-03-28 16:02 yan-liu
2017-03-17 18:34 yan-liu

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=20180424165534.GF15846@edge \
    --to=denys@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=yan-liu@ti.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.