From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables: build updates and fixes
Date: Fri, 30 Dec 2011 12:58:49 +0100 [thread overview]
Message-ID: <20111230115849.GC12204@1984> (raw)
In-Reply-To: <1325208902-2014-1-git-send-email-jengelh@medozas.de>
On Fri, Dec 30, 2011 at 02:34:55AM +0100, Jan Engelhardt wrote:
>
> The following changes since commit b8c42eca0f224a00bf55b60ded81af14a1e07da1:
> libiptc: provide separate pkgconfig files (2011-12-18 02:52:32 +0100)
>
> are available FOR REVIEW in the git repository at:
> git://dev.medozas.de/iptables stable
>
> Jan Engelhardt (6):
> Update .gitignore
> build: use AC_CONFIG_AUX_DIR and stash away tools
> Update .gitignore
> build: use delayed expansion on the user-settable variables
> extensions: link on libxtables and check symbols
> nfnl_osf: add missing libnfnetlink_CFLAGS to compile process
No objections regarding this patchset.
Only thing is that I'd like to reduce the changes on the -stable branch
to the strictly neccessary.
This is the only way to reduce the chances that someone comes and say
that we have broken something in -stable.
Would you be OK if this goes to master instead?
next prev parent reply other threads:[~2011-12-30 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 1:34 iptables: build updates and fixes Jan Engelhardt
2011-12-30 1:34 ` [PATCH 1/6] Update .gitignore Jan Engelhardt
2011-12-30 1:34 ` [PATCH 2/6] build: use AC_CONFIG_AUX_DIR and stash away tools Jan Engelhardt
2011-12-30 1:34 ` [PATCH 3/6] Update .gitignore Jan Engelhardt
2011-12-30 1:34 ` [PATCH 4/6] build: use delayed expansion on the user-settable variables Jan Engelhardt
2011-12-30 1:35 ` [PATCH 5/6] extensions: link on libxtables and check symbols Jan Engelhardt
2011-12-30 1:35 ` [PATCH 6/6] nfnl_osf: add missing libnfnetlink_CFLAGS to compile process Jan Engelhardt
2011-12-30 11:58 ` Pablo Neira Ayuso [this message]
2011-12-30 13:19 ` iptables: build updates and fixes Jan Engelhardt
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=20111230115849.GC12204@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--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).