From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Builds Failing
Date: Tue, 14 Jun 2011 18:57:48 -0700 [thread overview]
Message-ID: <4DF8119C.2000106@mentor.com> (raw)
In-Reply-To: <1308007647883960500@rkmorris.us>
On 06/13/2011 04:27 PM, Russell Morris wrote:
> Hi,
> Perhaps a dumb question, but ... do I need to do this? I can give it a try (though I'm not quite sure I understand what needs to be changed). Just trying to figure out how to get this working again.
> Thanks!
Since you have a failing setup, yes, please :)
To make git be used as the patch tool, add
PATCHTOOL = "git" to the recipe, increase the PR and add a comment about
why we do this.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-06-15 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 21:21 Builds Failing Russell Morris
2011-06-08 7:33 ` Khem Raj
2011-06-08 12:42 ` Russell Morris
2011-06-08 18:28 ` Tom Rini
2011-06-13 23:27 ` Russell Morris
2011-06-15 1:57 ` Tom Rini [this message]
2011-06-19 20:26 ` Russell Morris
2011-07-03 21:41 ` Russell Morris
2011-07-04 13:59 ` Russell Morris
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=4DF8119C.2000106@mentor.com \
--to=tom_rini@mentor.com \
--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