netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andy Spencer <andy753421@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables: use autoconf to process .in man pages
Date: Wed, 29 May 2013 19:40:44 +0200	[thread overview]
Message-ID: <20130529174044.GA7556@localhost> (raw)
In-Reply-To: <20130520030106.GA15853@pileus.org>

On Mon, May 20, 2013 at 03:01:06AM +0000, Andy Spencer wrote:
> This fixes a bug in iptables.8 and ip6tables.8 where @PACKAGE_VERSION@
> was not processed in the VERSION section. It also simplifies the
> Makefile by avoiding some sed commands.

Applied, thanks Andy.

> ---
> Yea, I don't know how I feel about having a .in.in, but it seems to work
> well enough.

I renamed the .in.in to .tmpl.in. After the the package version is
set, we got a template file which is later on populated with the
extensions. Just comestic change to avoid that.

      reply	other threads:[~2013-05-29 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20  3:01 [PATCH] iptables: use autoconf to process .in man pages Andy Spencer
2013-05-29 17:40 ` Pablo Neira Ayuso [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=20130529174044.GA7556@localhost \
    --to=pablo@netfilter.org \
    --cc=andy753421@gmail.com \
    --cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).