public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pull request - cups 2.0.3
Date: Fri, 17 Jul 2015 17:47:35 +0200	[thread overview]
Message-ID: <1437148055.3316.5.camel@ipfire.org> (raw)
In-Reply-To: <55A9217E.6070508@t-online.de>

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

Hi,

this looks good.

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.

On your note about testers: It seems that we do not have anyone on the
team who is actually using CUPS in a productive environment.

I also would appreciate if you could send in your changes as patches to
this list eventually. Take your time to figure out how this works: 
http://wiki.ipfire.org/devel/submit-patches

Best,
-Michael

On Fri, 2015-07-17 at 17:38 +0200, Matthias Fischer wrote:
> Hi list,
> 
> I prepared an update for cups.
> 
> cups - Update to 2.0.3:
> http://git.ipfire.org/?p=people/mfischer/ipfire
> -2.x.git;a=commit;h=a51f6ccd2637c30e3d31f30028583635cba38c4f
> 
> This solves https://bugzilla.ipfire.org/show_bug.cgi?id=10899 - 
> hopefully. ;-)
> 
> Regards
> Matthias

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

  reply	other threads:[~2015-07-17 15:47 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 [this message]
2015-07-17 20:25   ` Matthias Fischer
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=1437148055.3316.5.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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