From: Jan Engelhardt <jengelh@inai.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Assorted fixes v3
Date: Fri, 8 Feb 2013 02:11:29 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.01.1302080204350.10433@nerf07.vanv.qr> (raw)
In-Reply-To: <20130207185330.GA18719@localhost>
On Thursday 2013-02-07 19:53, Pablo Neira Ayuso wrote:
>> ----------------------------------------------------------------
>> Jan Engelhardt (4):
>> build: bump SONAME for libxtables
>
>Applied this one, thanks a lot for catching up this.
>
>> libxtables: centralize checking for a .save function
>> extensions: eui64: set userspacesize=0
>> iptables: fall back to using save function when print is not defined
>
>Not applying these, they are not fixes, sorry.
If you say so. (But it would have been nice to get told that the first time.)
Now, I can't put these onto nf/next without someone having to go through
a merge conflict later on, so besides getting put on hold again,
what is the preferable action?
prev parent reply other threads:[~2013-02-08 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 0:47 Assorted fixes v3 Jan Engelhardt
2013-02-06 0:47 ` [PATCH 1/4] build: bump SONAME for libxtables Jan Engelhardt
2013-02-06 0:47 ` [PATCH 2/4] libxtables: centralize checking for a .save function Jan Engelhardt
2013-02-06 0:47 ` [PATCH 3/4] extensions: eui64: set userspacesize=0 Jan Engelhardt
2013-02-06 0:47 ` [PATCH 4/4] iptables: fall back to using save function when print is not defined Jan Engelhardt
2013-02-07 18:53 ` Assorted fixes v3 Pablo Neira Ayuso
2013-02-08 1:11 ` Jan Engelhardt [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=alpine.LNX.2.01.1302080204350.10433@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.