From: Eric Leblond <eric@regit.org>
To: netfilter-devel@vger.kernel.org
Cc: eric@regit.org
Subject: [Ulogd2 PATCH 4/4] Prepare release number to 2.0.2
Date: Fri, 22 Feb 2013 11:25:58 +0100 [thread overview]
Message-ID: <1361528758-16674-5-git-send-email-eric@regit.org> (raw)
In-Reply-To: <1361528758-16674-1-git-send-email-eric@regit.org>
Update release number and fill Changes file.
Signed-off-by: Eric Leblond <eric@regit.org>
---
Changes | 9 +++++++++
configure.ac | 2 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/Changes b/Changes
index e59322c..3552b11 100644
--- a/Changes
+++ b/Changes
@@ -1,3 +1,12 @@
+Version 2.0.2 (2013-02-21)
+ - Add Graphite output module
+ - Update postgresql schema
+ - Add nfct filtering capabilities
+ - Add -v option to display message on sdtout
+ - Add -l option to specify verbosity on command line
+ - Build system improvements
+ - Fix parsing of ipv6 flowlabel and tc fields
+
Version 2.00alpha (2004-Oct-03)
- Total re-work. ulogd2 is almost unrelated to the ULOG netfilter target.
Instead, it has become a generic logging framework for anything from
diff --git a/configure.ac b/configure.ac
index df0e9d3..c94704b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,5 +1,5 @@
dnl Process this file with autoconf to produce a configure script.
-AC_INIT([ulogd], [2.0.1])
+AC_INIT([ulogd], [2.0.2])
AC_PREREQ([2.50])
AC_CONFIG_AUX_DIR([build-aux])
AM_INIT_AUTOMAKE([-Wall foreign tar-pax no-dist-gzip dist-bzip2 1.10b])
--
1.7.10.4
next prev parent reply other threads:[~2013-02-22 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 10:25 [Ulogd2 PATCH 0/4] preparing 2.0.2 release Eric Leblond
2013-02-22 10:25 ` [Ulogd2 PATCH 1/4] Add Changes to extra dist Eric Leblond
2013-02-22 10:25 ` [Ulogd2 PATCH 2/4] Update man page Eric Leblond
2013-02-22 10:25 ` [Ulogd2 PATCH 3/4] Update README Eric Leblond
2013-02-22 10:25 ` Eric Leblond [this message]
2013-02-25 7:18 ` [Ulogd2 PATCH 0/4] preparing 2.0.2 release Eric Leblond
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=1361528758-16674-5-git-send-email-eric@regit.org \
--to=eric@regit.org \
--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 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.