netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Vinson <nvinson234@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] nft: configure.ac: Replace magic dblatex dep.
Date: Sat, 2 Jul 2016 11:40:49 -0700	[thread overview]
Message-ID: <b75d6d02-3cc6-6058-4022-bde1e70a8aa8@gmail.com> (raw)
In-Reply-To: <20160701141546.GA8164@salvia>


[-- Attachment #1.1: Type: text/plain, Size: 1059 bytes --]

I reversed the logic.  I'm also considering this thread closed.  The new
thread can be found with the subject "[PATCH 1/1 rev.1] nft:
configure.ac: Replace magic dblatex dep."  If anyone could direct any
further questions or comments to that thread, it would be much appreciated.

Thanks,
Nicholas Vinson

On 07/01/2016 07:15 AM, Pablo Neira Ayuso wrote:
> On Sat, Jun 25, 2016 at 09:28:09AM -0700, Nicholas Vinson wrote:
>> Add a configure switch to enable and disable PDF document generation.
>> This switch is to replace the current method of automatically detecting
>> dblatex and building the PDF documentation when present.
> 
> I know I mentioned it was better to default this to yes on the
> bugzilla report, but I noticed this will just break many existing
> automated build infrastructure for everyone that have silently skipped
> building this.
> 
> So could you reverse the logic? I'd suggest something like:
> 
>         --enable-pdf-doc
> 
> so the PDF documentation building is disabled by default.
> 
> Thanks.
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-07-02 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25 16:28 [PATCH 1/1] nft: configure.ac: Replace magic dblatex dep Nicholas Vinson
2016-07-01 14:15 ` Pablo Neira Ayuso
2016-07-02 18:40   ` Nick Vinson [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=b75d6d02-3cc6-6058-4022-bde1e70a8aa8@gmail.com \
    --to=nvinson234@gmail.com \
    --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 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).