All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jeremy Sowden <jeremy@azazel.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] main: add more information to `nft -V`.
Date: Thu, 5 Mar 2020 12:47:07 +0100	[thread overview]
Message-ID: <20200305114707.jvofthwfvt2tdkkh@salvia> (raw)
In-Reply-To: <20200304085735.GA19243@azazel.net>

On Wed, Mar 04, 2020 at 08:57:35AM +0000, Jeremy Sowden wrote:
> On 2020-03-04, at 00:23:41 +0100, Pablo Neira Ayuso wrote:
> > From: Jeremy Sowden <jeremy@azazel.net>
> >
> > In addition to the package-version and release-name, output the CLI
> > implementation (if any) and whether mini-gmp was used, e.g.:
> >
> >     $ ./src/nft -V
> >     nftables v0.9.3 (Topsy)
> >       cli:          linenoise
> >       minigmp:      no
> >
> > Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > ---
> > Hi Jeremy et al.
> >
> > I'm revisiting this one, it's basically your patch with a few
> > mangling.
> >
> > I wonder if it's probably a good idea to introduce a long version
> > mode.  I have seen other tools providing more verbose information
> > about all build information.
> >
> > The idea would be to leave -v/--version as it is, and introduce -V
> > which would be more verbose.
> >
> > Thanks.
> 
> Fine by me.  Btw, I notice that OPTSTRING contains a couple of
> duplicates.  I've attached a patch to remove them.  It applies on top of
> this one.

Thanks, I have applied these two patches.

      reply	other threads:[~2020-03-05 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 23:23 [PATCH nft] main: add more information to `nft -V` Pablo Neira Ayuso
2020-03-04  8:57 ` Jeremy Sowden
2020-03-05 11:47   ` 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=20200305114707.jvofthwfvt2tdkkh@salvia \
    --to=pablo@netfilter.org \
    --cc=jeremy@azazel.net \
    --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.