From: Peter Volkov <pva@gentoo.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables branch management
Date: Fri, 09 Sep 2011 13:31:45 +0400 [thread overview]
Message-ID: <1315560705.10959.3.camel@tablet> (raw)
In-Reply-To: <alpine.LNX.2.01.1109081610030.6362@frira.zrqbmnf.qr>
В Чтв, 08/09/2011 в 16:41 +0200, Jan Engelhardt пишет:
> Oh we are nicely accumulating fixes & trivials already - do not worry
> about that. Just let me pull this off, all it means is that
> there is another branch head on iptables.git, and something convenient
> for the release manager to tag should the need arise for a .y release.
> Users already seem to like the idea[1].
> [1] http://marc.info/?l=netfilter-devel&m=131499886708085&w=2
As the iptables maintainer in Gentoo I really appreciate such branch
management. BTW, I'd like to know how long stable branch will be
maintained? Or IOW how we'll find out that it's not maintained any more?
With best regards,
--
Peter.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-09 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 14:20 iptables branch management Jan Engelhardt
2011-09-02 21:27 ` Maciej Żenczykowski
2011-09-05 17:54 ` Pablo Neira Ayuso
2011-09-08 10:05 ` Patrick McHardy
2011-09-08 11:59 ` Jan Engelhardt
2011-09-08 12:52 ` Patrick McHardy
2011-09-08 14:41 ` Jan Engelhardt
2011-09-08 14:58 ` Patrick McHardy
2011-09-09 9:31 ` Peter Volkov [this message]
2011-09-09 11:07 ` Jan Engelhardt
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=1315560705.10959.3.camel@tablet \
--to=pva@gentoo.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).