From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ulogd: build fixes
Date: Tue, 5 Jun 2012 19:01:59 +0200 [thread overview]
Message-ID: <20120605170159.GB25654@1984> (raw)
In-Reply-To: <1338885663-30131-1-git-send-email-jengelh@inai.de>
On Tue, Jun 05, 2012 at 10:41:00AM +0200, Jan Engelhardt wrote:
>
> The following changes since commit 5dc52c43c4d9e0e8a6813cdcd8e1d12a9f1e3fe8:
>
> build: use pkglibdir instead of pkglibexecdir for automake (2012-05-18 02:50:11 +0200)
>
> are available in the git repository at:
> git://git.inai.de/ulogd master
>
> Jan Engelhardt (3):
> sqlite: resolve compiler warnings
> nfacct: resolve build failure
> pcap: resolve unreliable detection
This is pretty convenient. Thanks a lot Jan.
Let's see if I find the time to release ulogd 2.0 by end of this week.
prev parent reply other threads:[~2012-06-05 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 8:41 ulogd: build fixes Jan Engelhardt
2012-06-05 8:41 ` [PATCH 1/3] sqlite: resolve compiler warnings Jan Engelhardt
2012-06-05 8:41 ` [PATCH 2/3] nfacct: resolve build failure Jan Engelhardt
2012-06-05 8:41 ` [PATCH 3/3] pcap: resolve unreliable detection Jan Engelhardt
2012-06-05 17:01 ` Pablo Neira Ayuso [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=20120605170159.GB25654@1984 \
--to=pablo@netfilter.org \
--cc=jengelh@inai.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).