From: Peter Seebach <peter.seebach@windriver.com>
To: Christopher Larson <kergoth@gmail.com>
Cc: Christopher Larson <chris_larson@mentor.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pseudo: obey our LDFLAGS
Date: Thu, 12 May 2016 13:24:06 -0500 [thread overview]
Message-ID: <20160512132406.12f33a04@seebs-worktop> (raw)
In-Reply-To: <1462983927-19691-1-git-send-email-kergoth@gmail.com>
On Wed, 11 May 2016 09:25:27 -0700
Christopher Larson <kergoth@gmail.com> wrote:
> +Subject: [PATCH] Obey external LDFLAGS the way we obey CFLAGS
This has been merged into pseudo's upstream, now, but it's on top of some
large changes, so we should probably go ahead with the local patch until
later.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2016-05-12 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 16:25 [PATCH] pseudo: obey our LDFLAGS Christopher Larson
2016-05-11 16:33 ` Mark Hatle
2016-05-11 17:14 ` Christopher Larson
2016-05-11 18:15 ` Mark Hatle
2016-05-11 18:24 ` Christopher Larson
2016-05-12 18:24 ` Peter Seebach [this message]
2016-05-13 16:27 ` Richard Purdie
2016-05-13 16:30 ` Christopher Larson
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=20160512132406.12f33a04@seebs-worktop \
--to=peter.seebach@windriver.com \
--cc=chris_larson@mentor.com \
--cc=kergoth@gmail.com \
--cc=openembedded-core@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