From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables branch management
Date: Thu, 08 Sep 2011 16:58:43 +0200 [thread overview]
Message-ID: <4E68D823.60306@trash.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1109081610030.6362@frira.zrqbmnf.qr>
Am 08.09.2011 16:41, schrieb Jan Engelhardt:
>
> On Thursday 2011-09-08 14:52, Patrick McHardy wrote:
>>>
>>> Nothing wrong, it just has not been done consistently or at all in the
>>> past. I believe it does not hurt to go ahead with this, also since I am
>>> statistically taking care of most submissions these days anyway.
>>
>> What has been done in the past doesn't really matter, we can of course
>> agree to have a stable branch when needed. But I don't see the point of
>> having a stable branch as long as it doesn't contain any fixes.
>
> 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
>
Sure, go ahead.
next prev parent reply other threads:[~2011-09-08 14:59 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 [this message]
2011-09-09 9:31 ` Peter Volkov
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=4E68D823.60306@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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 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.