From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Florian Westphal <fw@strlen.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [ANNOUNCE] libnetfilter_queue 1.0.5 release
Date: Fri, 12 Jun 2020 13:56:11 +0200 [thread overview]
Message-ID: <20200612115611.GA31175@salvia> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2006121333320.11258@n3.vanv.qr>
On Fri, Jun 12, 2020 at 01:34:15PM +0200, Jan Engelhardt wrote:
>
> On Friday 2020-06-12 13:32, Jan Engelhardt wrote:
> >On Friday 2020-06-12 12:24, Florian Westphal wrote:
> >>
> >>The only change compared to version 1.0.4 is releated to documentation.
> >>To build/install doxygen documentation, you will now need to pass the
> >>"--with-doxygen" option to the "configure" script.
> >>
> >>There are no changes to the library itself.
> >>
> >>You can download it from:
> >>
> >>https://www.netfilter.org/projects/libnetfilter_queue/downloads.html
> >
> >So what will happen to http://ftp.netfilter.org/pub/libnetfilter_queue/ ?
> >I kind of like the autogenerated directory index to look at
> >(not scripted, really just as a human). It provides versions and release
> >dates in one view and you can just pick up any one of them (for historic
> >research purposes or whatever), without having to engage in a conversation with
> >the rsync command line.
> >
> >Such a dirindex could also be provided by www.netfilter.org, considering
> >the shutdown plans of the ftp service (or the ftp host itself?).
>
> Oh silly me. Trivially found.
> http://netfilter.org/projects/libnetfilter_queue/files/, derived from the
> current 1.0.5 tarball link, is just fine.
There is also:
https://www.netfilter.org/pub/
prev parent reply other threads:[~2020-06-12 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 10:24 [ANNOUNCE] libnetfilter_queue 1.0.5 release Florian Westphal
2020-06-12 11:32 ` Jan Engelhardt
2020-06-12 11:34 ` Jan Engelhardt
2020-06-12 11:56 ` 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=20200612115611.GA31175@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--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 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.