All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Guruswamy Basavaiah <guru2018@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables-translate: Printing the table name before chain name
Date: Thu, 7 Apr 2016 11:50:23 +0200	[thread overview]
Message-ID: <20160407095023.GA2959@salvia> (raw)
In-Reply-To: <20160405070837.GA12017@inbhdhcp21574.apac.nsn-net.net>

On Tue, Apr 05, 2016 at 12:38:37PM +0530, Guruswamy Basavaiah wrote:
> Printing the table name before chain name.
> 
> Command ./iptables-restore-translate, was printing
> table name before the chain name for user added chains.
> This is breaking ./nft -f command.
> 
> Before fix, output of "./iptables-restore-translate"
> add chain ip OUTPUT_direct raw
> 
> After fix:
> add chain ip raw OUTPUT_direct

I want to take this fix, but it doesn't apply:

$ git am /tmp/iptables-translate-Printing-the-table-name-before-chain-name.patch -s
Applying: iptables-translate: Printing the table name before chain name
error: patch failed: iptables/xtables-translate.c:296
error: iptables/xtables-translate.c: patch does not apply
Patch failed at 0001 iptables-translate: Printing the table name before chain name
The copy of the patch that failed is found in:
   /home/pablo/devel/scm/git-netfilter/iptables/.git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".


  reply	other threads:[~2016-04-07  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  7:08 [PATCH] iptables-translate: Printing the table name before chain name Guruswamy Basavaiah
2016-04-07  9:50 ` Pablo Neira Ayuso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-05  6:28 Guruswamy Basavaiah

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=20160407095023.GA2959@salvia \
    --to=pablo@netfilter.org \
    --cc=guru2018@gmail.com \
    --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 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.