On Sun, Sep 30, 2012 at 12:22:03PM +0200, Jan Engelhardt wrote: > > Hi, > > > It was that time of the year again to process reports from the > Debian bug tracking system. :) > > === > The following changes since commit 0d701631625898ac33fb53c67ed2b529668fe0d7: > > libxt_state: replace as an alias to xt_conntrack (2012-09-30 11:21:25 +0200) > > are available in the git repository at: > > git://git.inai.de/iptables master > > for you to fetch changes up to 6cf011116fc4752cde75eabe3b1b3f2a93ae27bd: > > src: remove faulty deprecated marker in libipt_LOG source (2012-09-30 12:17:31 +0200) All patches but: iptables: fix order of internal commands list look fine to me. For iptables-restore: kill unused -b option I'd be more conservative, ie. spotting a warning to say that the option is meaningless (so we make sure we don't break stupid scripts). Apart from that, all OK. Please feel free to add: Acked-by: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> Thanks for your updates Jan. > ---------------------------------------------------------------- > Jan Engelhardt (17): > doc: clean up interpunction in state list for xt_conntrack > doc: deduplicate extension descriptions into a new manpage > doc: trim "state" manpage and reference conntrack instead > doc: have NOTRACK manpage point to CT instead > doc: mention iptables-apply in the SEE ALSO sections > iptables: fix order of internal commands list > iptables: implement --line-numbers for iptables -S > iptables-restore: kill unused -b option > doc: rename .8.in files to .8in > doc: add package version to all manpages > doc: fixup omissions in ip6tables-restore.8 > doc: document iptables-restore's -t option > doc: document iptables-restore's -v option > doc: document iptables-restore's -M option > doc: document iptables-restore's -h option > doc: name the supported log levels for ipt_LOG > src: remove faulty deprecated marker in libipt_LOG source -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
