netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Netfilter Devel <netfilter-devel@vger.kernel.org>
Cc: netdev@vger.kernel.org, netfilter@vger.kernel.org,
	netfilter-announce@lists.netfilter.org, lwn@lwn.net
Subject: [ANNOUNCE] ulogd 2.0.5 release
Date: Sun, 10 May 2015 21:40:35 +0200	[thread overview]
Message-ID: <1431286835.21627.3.camel@regit.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 563 bytes --]

Hi!

The Netfilter project proudly presents:

	ulogd 2.0.5

This release fixes build on recent systems where Linux headers don't
contain anymore ULOG header files. It also fixes JSON output on big
endian system.

A big thanks to Jimmy Jones, Vincent Bernat for their contributions. See
ChangeLog that comes attached to this email for more details.

You can download it from:

http://www.netfilter.org/projects/ulogd/downloads.html
ftp://ftp.netfilter.org/pub/ulogd/

Have fun!
-- 
Eric Leblond <eric@regit.org>
Blog: https://home.regit.org/

[-- Attachment #1.2: changes-ulogd-2.0.5.txt --]
[-- Type: text/plain, Size: 385 bytes --]

Eric Leblond (4):
      gitignore: add manpage
      Set release number to 2.0.5.
      Add flag to disable ULOG input plugin
      Add missing enableval to configure

Jimmy Jones (1):
      Fix JSON output on big endian systems

Pablo Neira Ayuso (1):
      include: keep a copy of linux/netfilter_ipv4/ipt_ULOG.h

Vincent Bernat (1):
      gitignore: ignore generated documentation


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

                 reply	other threads:[~2015-05-10 19:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1431286835.21627.3.camel@regit.org \
    --to=eric@regit.org \
    --cc=lwn@lwn.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-announce@lists.netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@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).