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: [PATCH 1/3] iptables: accept multiple IP address specifications for -s, -d
Date: Fri, 17 Jul 2009 16:31:23 +0200 [thread overview]
Message-ID: <4A608B3B.20702@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0907161624140.22115@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2009-06-25 19:08, Jan Engelhardt wrote:
>> On 2009-06-10 12:19:59, Patrick wrote:
>>> On Wednesday 2009-06-10 14:16, Jan Engelhardt wrote:
>>>> Git is not as castrated as Hg when it comes to branches, so why not
>>>> make a "stable" branch that is then regularly merged into master? :)
>>> I don't see why that would currently be necessary. We're talking
>>> about a few days, and in fact I'd rather have people test the
>>> current code before the release instead of hacking on new things :)
>> Yeah but in general? The - judging from their version numbers -
>> x.y.z.S stable versions like 1.4.3.1 used to receive lots of new
>> features because there is just master, in which case it should
>> have been the new 1.4.4 already.
>> So either z is bumped more often and S-versions will not
>> be released, or S only receives fixes, necessiting a separate branch.
>> Objections?
>
> It would be cool to get an answer here so I know how to twingle
> patchbranches that I'd like to submit.
Well, I don't object to having a stable branch when we actually do
need to release pure bug-fix versions. But I'd say those can be
created on demand.
next prev parent reply other threads:[~2009-07-17 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:25 iptables: pull request June-05 Jan Engelhardt
2009-06-05 19:25 ` [PATCH 1/3] iptables: accept multiple IP address specifications for -s, -d Jan Engelhardt
2009-06-06 6:53 ` Pablo Neira Ayuso
2009-06-06 11:16 ` Jan Engelhardt
2009-06-07 21:12 ` Pablo Neira Ayuso
2009-06-08 13:50 ` Patrick McHardy
2009-06-10 12:16 ` Jan Engelhardt
2009-06-10 12:19 ` Patrick McHardy
2009-06-25 17:08 ` Jan Engelhardt
2009-07-16 14:24 ` Jan Engelhardt
2009-07-17 14:31 ` Patrick McHardy [this message]
2009-07-17 15:55 ` Jan Engelhardt
2009-06-05 19:25 ` [PATCH 2/3] DNAT/SNAT: add manpage documentation for --persistent flag Jan Engelhardt
2009-06-08 13:46 ` Patrick McHardy
2009-06-05 19:25 ` [PATCH 3/3] extensions: remove redundant casts Jan Engelhardt
2009-06-08 13:47 ` Patrick McHardy
2009-06-08 13:45 ` iptables: pull request June-05 Patrick McHardy
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=4A608B3B.20702@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 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).