netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@regit.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nfacct PATCH 0/1] Fix typo in cmd line parsing
Date: Mon, 16 Jul 2012 14:27:47 +0200	[thread overview]
Message-ID: <20120716122747.GA17585@1984> (raw)
In-Reply-To: <1342302032-9108-1-git-send-email-eric@regit.org>

On Sat, Jul 14, 2012 at 11:40:31PM +0200, Eric Leblond wrote:
> 
> Hello,
> 
> This patch fixes what looks like a typo in the command line parsing.
> I did not manage to find a good explanation to the current code and
> I thus decide to cool this little patch.

Applied, thanks Eric

You've fixed: nfacct list xml reset

that allows you to atomically get and reset counters while obtaining
them in XML.

      parent reply	other threads:[~2012-07-16 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14 21:40 [nfacct PATCH 0/1] Fix typo in cmd line parsing Eric Leblond
2012-07-14 21:40 ` [PATCH] Fix typo in loop Eric Leblond
2012-07-16 12:27 ` Pablo Neira Ayuso [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=20120716122747.GA17585@1984 \
    --to=pablo@netfilter.org \
    --cc=eric@regit.org \
    --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).