netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: Inclusion inquiry about remaining patches
Date: Wed, 24 Feb 2010 15:57:51 +0100	[thread overview]
Message-ID: <4B853E6F.2060709@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1002241411580.19195@obet.zrqbmnf.qr>

Jan Engelhardt wrote:
> On Wednesday 2010-02-24 13:41, Patrick McHardy wrote:
>>> there are about 70 patches left that I intended to submit, but it seems 
>>> Netfilter stagnated again this release. Is there still a chance for 
>>> inclusion in this round?
>> Well, the last batch didn't exactly fill me with confidence that
>> these patches have been sufficiently tested.
>>
>> I'll consider the cleanup batch if you can assure me that it
>> doesn't contain bugs similar to the "lost POSTROUTING chain"
>> problem contained in the last series that should have been
>> noticed with just some basic testing.
> 
> They have had their testing, and the error had been caught too
> by Changli merely by reading the patch:
> 
> http://marc.info/?l=netfilter-devel&m=125732159605634&w=2
> http://marc.info/?l=netfilter-devel&m=125733769630550&w=2
> 
> I still have blob 685400 in my working copy, though it seems unreachable 
> at this time, which means it sometime got lost in a rebase.

OK fair enough, I'll have another look once I'm finished with
my current work.

      reply	other threads:[~2010-02-24 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 10:18 Inclusion inquiry about remaining patches Jan Engelhardt
2010-02-24 12:41 ` Patrick McHardy
2010-02-24 14:48   ` Jan Engelhardt
2010-02-24 14:57     ` Patrick McHardy [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=4B853E6F.2060709@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.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 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).