All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes
Date: Thu, 04 Jun 2015 11:58:02 -0500	[thread overview]
Message-ID: <5570839A.9050704@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZkSUFvQWm2zL25keDCZYq0h_iW==5F8a+RKdmnpCcgmw@mail.gmail.com>



On 04/06/15 11:54, Burton, Ross wrote:
> On 4 June 2015 at 17:54, Aníbal Limón <anibal.limon@linux.intel.com> wrote:
>
>> The problem is i forget to add v2 to the patch [1] that is a new version
>> of the patch [2], sorry
>> about that.
>>
> The problem is we merged v1 of that patch into master.  Can you rebase and
> fix what's in master?
Sure,
     alimon
>
> Ross
>



      reply	other threads:[~2015-06-04 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 19:49 [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes Aníbal Limón
2015-06-02 19:49 ` [PATCH 1/4] recipeutils: Add get_recipe_upstream_version and get_recipe_pv_without_srcpv functions Aníbal Limón
2015-06-02 19:49 ` [PATCH 2/4] distrodata: Remove unnecessary include of package_regex.inc Aníbal Limón
2015-06-02 19:49 ` [PATCH 3/4] distrodata: checkpkg make usage of oe.recipeutils.get_recipe_upstream_version Aníbal Limón
2015-06-02 19:49 ` [PATCH 4/4] distrodata: Use Python CSV instead of did by hand Aníbal Limón
2015-06-04 16:09 ` [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes Burton, Ross
2015-06-04 16:54   ` Aníbal Limón
2015-06-04 16:54     ` Burton, Ross
2015-06-04 16:58       ` Aníbal Limón [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=5570839A.9050704@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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.