Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Kelly <mkelly@xevo.com>
To: "dvhart@vmware.com" <dvhart@vmware.com>
Cc: "koen@dominion.thruhere.net" <koen@dominion.thruhere.net>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 00/14] new recipe: open-vm-tools recipe
Date: Mon, 19 Jun 2017 22:02:55 +0000	[thread overview]
Message-ID: <1497909741.4988.2.camel@xevo.com> (raw)
In-Reply-To: <B110778A-770D-46DC-9394-09B1919F6C51@vmware.com>

On Fri, 2017-06-16 at 21:53 +0000, Darren Hart wrote:
> On 06/09/2017 03:22 PM, Martin Kelly wrote:
> > Hi all,
> > 
> > This patch series adds a new recipe for Open VM Tools to meta-oe.
> > This recipe is invaluable for using Openembedded with VMWare, as
> > without the tools, performance is very slow.
> > More information about Open VM Tools can be found here:
> > 
> > 
> > https://github.com/vmware/open-vm-tools
> > 
> > 
> > 
> > Please note that, as mentioned in the first commit, this recipe is
> > modified from the recipe originally found in the Open-Switch
> > repository. The first patch is directly from that repository, and
> > the following patches are modifications to it.
> 
> Hi all,
> 
> Please forgive me if this doesn’t land on the mailing list quite
> right. I am no longer subscribed to this list and replying from web
> archives can be hit and miss.
> 
> I wanted to reach out and say it’s great to see this recipe being
> submitted to meta-oe, and nice work updating the recipe meta-data.
> 
> If there is something we can do to help make this easier to maintain,
> support, etc, please don’t hesitate to reach out to me. I noticed,
> for example, there are a few patches to deal with deprecated library
> calls and the OE build environment.
> 

Thanks, will do. There's a few patches that should probably go upstream
if they're not already present in some other form.

> Finally… as the author of send-pull-request, I have to confess a
> twinge of guilt when it failed you Martin. If you want to send me
> details on how you ran it and the details of the failure, I’d be
> happy to look into it.
> 
> One possibility is that your local branch didn’t match the remote
> branch. Another possibility is that it isn’t parsing the GitHub
> repository location correctly, and that may need updating.
> 

Thanks; as you may have seen, I need to make a few changes due to
issues that Martin Jansa found. I will try send-pull-request again and
send you details about any issues I hit.

> Thanks,
> 
> --
> Darren Hart
> Director / Open Source Architect
> VMware Open Source Technology Center
> 

       reply	other threads:[~2017-06-19 22:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B110778A-770D-46DC-9394-09B1919F6C51@vmware.com>
2017-06-19 22:02 ` Martin Kelly [this message]
2017-06-09 22:22 [meta-oe][PATCH 00/14] new recipe: open-vm-tools recipe Martin Kelly
2017-06-15 16:36 ` Martin Kelly
2017-06-15 16:54   ` Martin Jansa
2017-06-15 17:07     ` Martin Kelly
2017-06-15 17:17       ` Martin Jansa
2017-06-15 17:22         ` Martin Kelly
2017-06-23  7:41         ` Paul Eggleton
2017-06-23 17:20           ` Darren Hart
2017-06-15 17:40     ` Martin Kelly
2017-06-15 17:50       ` Martin Jansa
2017-06-18 19:58         ` Martin Jansa
2017-06-18 20:28           ` Martin Jansa
2017-06-19 23:43             ` Martin Kelly
2017-06-22 17:15               ` Martin Kelly
2017-06-22 17:32                 ` Martin Jansa
2017-06-22 18:21                   ` Martin Kelly
2017-06-23 10:33                     ` Martin Jansa
2017-06-23 23:51                       ` Martin Kelly
2017-06-19 18:35           ` Martin Kelly

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=1497909741.4988.2.camel@xevo.com \
    --to=mkelly@xevo.com \
    --cc=dvhart@vmware.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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