From: Tim Waugh <twaugh@redhat.com>
To: Michael Sweet <msweet@apple.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] CUPS 'marker-low-levels' attribute question
Date: Mon, 24 Feb 2014 17:48:27 +0000 [thread overview]
Message-ID: <1393264107.2696.17.camel@rubik> (raw)
In-Reply-To: <C7A94624-AB3F-496C-9BDA-E0C9B9E2E2A2@apple.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Mon, 2014-02-24 at 12:37 -0500, Michael Sweet wrote:
> The intent is that marker-low-levels is the point at which you report
> marker-supply-low-warning and marker-high-levels is the point at which
> you report marker-waste-almost-full-warning.
>
> Put more simply, if the marker-levels value is outside the range
> reported by marker-low-levels and marker-high-levels, then you need to
> do (replace) something soon.
Thanks, I see now.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2014-02-24 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:34 [Printing-architecture] CUPS 'marker-low-levels' attribute question Tim Waugh
2014-02-24 17:37 ` Michael Sweet
2014-02-24 17:48 ` Tim Waugh [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=1393264107.2696.17.camel@rubik \
--to=twaugh@redhat.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.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.