public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <fischerm42@t-online.de>
To: development@lists.ipfire.org
Subject: Re: Pull request - cups 2.0.3
Date: Fri, 17 Jul 2015 22:25:52 +0200	[thread overview]
Message-ID: <55A964D0.4070609@t-online.de> (raw)
In-Reply-To: <1437148055.3316.5.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hi,

On 17.07.2015 17:47, Michael Tremer wrote:

> I am just wondering why the two backend files for https and ipps are
> gone. Have these been merged with http or something else? Dropping
> support for those two protocols won't be a good idea.

I noticed this too, while editing the rootfile.

Do we need additional configure-options for https and ipps?

What about --enable-ssl, --enable-gnutls and --enable-cdsassl?

Regards
Matthias


  reply	other threads:[~2015-07-17 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 15:38 Matthias Fischer
2015-07-17 15:47 ` Michael Tremer
2015-07-17 20:25   ` Matthias Fischer [this message]
2015-07-18  7:03   ` [PATCH] cups: Update to 2.0.3 (was: Re: Pull request - cups 2.0.3) Matthias Fischer

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=55A964D0.4070609@t-online.de \
    --to=fischerm42@t-online.de \
    --cc=development@lists.ipfire.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