Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Dan McGregor <danismostlikely@gmail.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] dpkg: fix host contamination
Date: Thu, 15 Jan 2015 08:57:56 -0600	[thread overview]
Message-ID: <54B7D574.9030606@linux.intel.com> (raw)
In-Reply-To: <CACS+7ZQe+N6mWE8uPR2nmE8dcEtFjmzH8NfGfX_iVVgsp8y6eQ@mail.gmail.com>

Hi Dan,

Can you explain in the commit message what is this change needed?

On 14/01/15 21:51, Dan McGregor wrote:
> +EXTRA_OECONF_append_class-target = " TAR=tar"

Kind regards

     alimon


  reply	other threads:[~2015-01-15 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  3:51 [PATCH 3/3] dpkg: fix host contamination Dan McGregor
2015-01-15 14:57 ` Aníbal Limón [this message]
2015-01-15 15:27   ` Dan McGregor
2015-01-15 15:41   ` Dan McGregor
  -- strict thread matches above, loose matches on Subject: below --
2015-01-15 15:49 Dan McGregor

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=54B7D574.9030606@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=danismostlikely@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