From: "Koul, Vinod" <vinod.koul@intel.com>
To: "arun@accosted.net" <arun@accosted.net>
Cc: "git@arunraghavan.net" <git@arunraghavan.net>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [tinycompress] [PATCH] build: Fix make distcheck
Date: Thu, 8 Oct 2015 11:07:51 +0000 [thread overview]
Message-ID: <1444302471.25504.81.camel@intel.com> (raw)
In-Reply-To: <1444300888-30059-1-git-send-email-arun@accosted.net>
On Thu, 2015-10-08 at 11:41 +0100, arun@accosted.net wrote:
> From: Arun Raghavan <git@arunraghavan.net>
>
> srcdir may not be the same as builddir, so use the correct variable for
> the include path.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2015-10-08 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 10:41 [tinycompress] [PATCH] build: Fix make distcheck arun
2015-10-08 11:07 ` Koul, Vinod [this message]
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=1444302471.25504.81.camel@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun@accosted.net \
--cc=git@arunraghavan.net \
/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