From: David Miller <davem@davemloft.net>
To: kadlec@blackhole.kfki.hu
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset-5.2 released
Date: Thu, 23 Dec 2010 11:32:26 -0800 (PST) [thread overview]
Message-ID: <20101223.113226.102539649.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1012231553460.6044@blackhole.kfki.hu>
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Date: Thu, 23 Dec 2010 15:57:12 +0100 (CET)
> git://git.netfilter.org/ipset.git, ipset-5 branch
This is way more difficult than it should be.
People cannot just clone your tree to look at the latest code. The
master branch, which should be the latest and greatest, is your 4.x
stuff.
They have to go through a multi-step non-trivial process to get at the
latest 5.x code, and this is a serious discouragement.
It's frankly rediculious.
I personally did a "rm -rf ipset/" when I discovered how this was
setup, and I seriously wanted to review your code and look for bugs.
next prev parent reply other threads:[~2010-12-23 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 14:57 [ANNOUNCE] ipset-5.2 released Jozsef Kadlecsik
2010-12-23 19:32 ` David Miller [this message]
2010-12-23 19:48 ` Jozsef Kadlecsik
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=20101223.113226.102539649.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--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