public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Peter Osterlund <peter.osterlund@mailbox.swipnet.se>,
	linux-kernel@vger.kernel.org, linux-parport@torque.net
Subject: Re: Printing to off-line printer in 2.4.0-prerelease
Date: Thu, 4 Jan 2001 11:17:08 +0000	[thread overview]
Message-ID: <20010104111708.F23469@redhat.com> (raw)
In-Reply-To: <20010104014115.C6256@athlon.random> <Pine.LNX.4.30.0101040158310.3983-100000@ppro.localdomain> <20010104023921.A9503@athlon.random>
In-Reply-To: <20010104023921.A9503@athlon.random>; from andrea@suse.de on Thu, Jan 04, 2001 at 02:39:21AM +0100

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

On Thu, Jan 04, 2001 at 02:39:21AM +0100, Andrea Arcangeli wrote:

> On Thu, Jan 04, 2001 at 02:09:56AM +0100, Peter Osterlund wrote:
> > should say that it is obsolete. I think obsolete means "you should never
> > ever have to use this stuff".
> 
> Agreed.

I think that LP_CAREFUL is still needed.  There are printers that
think that nFault overrides the other error lines and there are
printers that drag nFault to 'okay to print' when off.  To keep
everyone happy (those that want to print to error-line-wreckless
printers, and those that want jobs being sent to a printer that's off
to wait until the printer comes online) I think we need LP_CAREFUL to
remain.

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-01-04 11:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 18:44 Printing to off-line printer in 2.4.0-prerelease Peter Osterlund
2001-01-03 19:13 ` Andrea Arcangeli
2001-01-03 21:00   ` Peter Osterlund
2001-01-03 21:35     ` Andrea Arcangeli
2001-01-04  0:08       ` Peter Osterlund
2001-01-04  0:41         ` Andrea Arcangeli
2001-01-04  1:09           ` Peter Osterlund
2001-01-04  1:39             ` Andrea Arcangeli
2001-01-04 11:17               ` Tim Waugh [this message]
2001-01-04  9:27         ` Tim Waugh
2001-01-04 13:50           ` Andrea Arcangeli
2001-01-04 11:20 ` Tim Waugh
2001-01-04 13:52   ` Andrea Arcangeli
2001-01-04 14:20     ` Tim Waugh
2001-01-04 14:39       ` Andrea Arcangeli
2001-01-04 14:54         ` Tim Waugh
2001-01-04 19:45           ` Peter Osterlund
2001-01-04 19:07       ` Peter Osterlund
2001-01-04 21:52         ` Tim Waugh
2001-01-05  0:33           ` Peter Osterlund
  -- strict thread matches above, loose matches on Subject: below --
2001-01-04 15:30 Jesse Pollard
2001-01-04 19:22 ` Gunther Mayer
2001-01-05  1:13   ` Jesse Pollard
2001-01-04 23:20 ` David Ford

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=20010104111708.F23469@redhat.com \
    --to=twaugh@redhat.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@torque.net \
    --cc=peter.osterlund@mailbox.swipnet.se \
    /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