From: Marcel Holtmann <marcel@holtmann.org>
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org, linux-nfc@lists.01.org
Subject: Re: [PATCH neard 2/2] build: Do not use deprecated AM_CONFIG_HEADER
Date: Thu, 10 Jan 2013 15:54:17 -0800 [thread overview]
Message-ID: <1357862057.1806.76.camel@aeonflux> (raw)
In-Reply-To: <1357831094-13513-2-git-send-email-lucas.demarchi@profusion.mobi>
Hi Lucas,
> The long-obsoleted AM_CONFIG_HEADER macro was removed in automake 1.13.
> Use AC_CONFIG_HEADERS instead.
> ---
> configure.ac | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
patch has been applied.
Regards
Marcel
next prev parent reply other threads:[~2013-01-10 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:18 [PATCH neard 1/2] build: Use AM_CPPFLAGS instead of INCLUDES Lucas De Marchi
2013-01-10 15:18 ` [PATCH neard 2/2] build: Do not use deprecated AM_CONFIG_HEADER Lucas De Marchi
2013-01-10 23:54 ` Marcel Holtmann [this message]
2013-01-10 23:54 ` [PATCH neard 1/2] build: Use AM_CPPFLAGS instead of INCLUDES Marcel Holtmann
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=1357862057.1806.76.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=lucas.demarchi@profusion.mobi \
/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;
as well as URLs for NNTP newsgroup(s).