All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: hadi@cyberus.ca, Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libxtables:  Introduce xtables_merge_options()
Date: Wed, 11 Feb 2009 16:08:30 +0100	[thread overview]
Message-ID: <4992E9EE.9050807@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902111606240.20223@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Wednesday 2009-02-11 16:05, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> On Wednesday 2009-02-11 13:07, Patrick McHardy wrote:
>>>
>>>> jamal wrote:
>>>>> Sorry, I said i wasnt gonna send more until i hear the ACKs/NACKs on all
>>>>> patches  but found myself with extra cycles; so i am sending 2-3 more.
>>>>> This one is for code reuse so i dont have to keep up in tc/ipt
>>>>> with the latest variant inside iptables.
>>>> I'll wait a few more hours before applying these to give other
>>>> people a chance to review them.
>>>>
>>> Bad for me who wakes up later than that hour  o_O
>> I haven't applied them yet ...
>>
> Something *did* add 8e90ce6..8b7baeb though.

Yes, I was referring to the last three patches.


  reply	other threads:[~2009-02-11 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 21:27 [PATCH] libxtables: Introduce xtables_merge_options() jamal
2009-02-11 12:07 ` Patrick McHardy
2009-02-11 15:04   ` Jan Engelhardt
2009-02-11 15:05     ` Patrick McHardy
2009-02-11 15:07       ` Jan Engelhardt
2009-02-11 15:08         ` Patrick McHardy [this message]
2009-02-11 15:27           ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2009-02-13 13:51 jamal
2009-02-13 13:58 ` 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=4992E9EE.9050807@trash.net \
    --to=kaber@trash.net \
    --cc=hadi@cyberus.ca \
    --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.