All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Fathi Boudra <fathi.boudra@linaro.org>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 1/7] ltp: rename recipe to ltp_20140115.bb
Date: Mon, 27 Jan 2014 13:37:25 -0800	[thread overview]
Message-ID: <52E6D195.8030809@linux.intel.com> (raw)
In-Reply-To: <CAGNsrLBebkDZcLk91x1XPAGW2XzK0opYgRJ7u8s4+Du32t_R9A@mail.gmail.com>

On 01/21/2014 04:17 AM, Fathi Boudra wrote:
> On 21 January 2014 12:41, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Mon, 2014-01-20 at 13:40 +0200, Fathi Boudra wrote:
>>> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
>>> ---
>>>   meta/recipes-extended/ltp/ltp_20130904.bb | 78 -------------------------------
>>>   meta/recipes-extended/ltp/ltp_20140115.bb | 78 +++++++++++++++++++++++++++++++
>>>   2 files changed, 78 insertions(+), 78 deletions(-)
>>>   delete mode 100644 meta/recipes-extended/ltp/ltp_20130904.bb
>>>   create mode 100644 meta/recipes-extended/ltp/ltp_20140115.bb
>>
>> So we rename the recipe but don't actually change the SRCREV to the new
>> version (since you do that in 3/7)?
>>
>> This seems a little confusing?
>
> could be :) I sent the patchset as-is. I can squash the 2 patches if you prefer.
>

Yes, please can you please send a v3 patch set, also might be nice to 
have the clean-ups first and then the changes that are new after the update.

Make sense?

Thanks
	Sau!

>> Cheers,
>>
>> Richard
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  reply	other threads:[~2014-01-27 21:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 11:40 [PATCHv2 0/7] ltp: update 20140115 release Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 1/7] ltp: rename recipe to ltp_20140115.bb Fathi Boudra
2014-01-21 10:41   ` Richard Purdie
2014-01-21 12:17     ` Fathi Boudra
2014-01-27 21:37       ` Saul Wold [this message]
2014-01-20 11:40 ` [PATCHv2 2/7] ltp: fix style using oe-stylize (no changes in the content of the recipe itself) Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 3/7] ltp: drop do_unpack_append/do_extract_tarball Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 4/7] ltp: update SRC_REV to LTP 20140115 release Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 5/7] ltp: update ffsb-6.0-rc2 license file path Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 6/7] ltp: fix comment to refer to oe-core instead of poky Fathi Boudra
2014-01-20 11:40 ` [PATCHv2 7/7] ltp: fix ffsb ftbfs on cross-compiled environment Fathi Boudra

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=52E6D195.8030809@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=fathi.boudra@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.