From: Darren Hart <dvhart@infradead.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 00/14] new recipe: open-vm-tools recipe
Date: Fri, 23 Jun 2017 10:20:26 -0700 [thread overview]
Message-ID: <20170623172026.GA29859@fury> (raw)
In-Reply-To: <5720950.qHQRHiQ22q@peggleto-mobl.ger.corp.intel.com>
On Fri, Jun 23, 2017 at 09:41:08AM +0200, Paul Eggleton wrote:
> On Thursday, 15 June 2017 7:17:18 PM CEST Martin Jansa wrote:
> > No problem, I had issues with that script as well, but it works for me if I
> > provide all necessary params manually (when it doesn't try to figure out
> > anything).
>
> Which issues have you been experiencing with send-pull-request? Have you
> reported these as bugs?
I had also reached out, but hadn't subscribed to the list yet. He said he would
respin the patches and provide specifics on the failure he experienced.
If I recall, it can still be picking about certain remotes, but I thought github
was one that it handled well. So I'm looking forward to seeing the report. Happy
to help once we have some details.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-06-23 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <B110778A-770D-46DC-9394-09B1919F6C51@vmware.com>
2017-06-19 22:02 ` 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=20170623172026.GA29859@fury \
--to=dvhart@infradead.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox