public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: tilman@imap.cc, rdunlap@xenotime.net,
	linux-usb-devel@lists.sourceforge.net, hjlipp@web.de,
	linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] reduce syslog clutter (take 2)
Date: Thu, 9 Mar 2006 13:03:27 -0800	[thread overview]
Message-ID: <20060309130327.32ef68de.akpm@osdl.org> (raw)
In-Reply-To: <9a8748490603091058l75aacacsfc5fdba3981fb074@mail.gmail.com>

"Jesper Juhl" <jesper.juhl@gmail.com> wrote:
>
> > Feb 21 00:12:13 gx110 kernel: gigaset: ISDN_CMD_SETL3: invalid protocol 42
>  >
>  > do not provide any useful information for that clientele. They just push
> 
>  The filename may not be useful to the user, but the instant the user decides to
>  submit a bugreport to LKML or elsewhere it becomes useful.

But OTOH, there's a difference between messages-to-developers (usually "the
code went wrong") and messages-to-users (hopefully usually "the hardware
went wrong" or "you went wrong").

So I guess the change is a good one for end-user informational messages. 
And end-users are the party who should be served, more than developers.

  parent reply	other threads:[~2006-03-09 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 22:54 [PATCH] reduce syslog clutter (take 2) Tilman Schmidt
2006-03-09  5:47 ` Randy.Dunlap
2006-03-09 10:15   ` Tilman Schmidt
2006-03-09 11:02 ` Andrew Morton
2006-03-09 16:34   ` Randy.Dunlap
2006-03-09 18:43     ` Tilman Schmidt
     [not found]       ` <9a8748490603091058l75aacacsfc5fdba3981fb074@mail.gmail.com>
2006-03-09 19:17         ` Tilman Schmidt
2006-03-09 21:03         ` Andrew Morton [this message]
2006-03-09 21:18           ` Pete Zaitcev
2006-03-09 22:42             ` Greg KH

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=20060309130327.32ef68de.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hjlipp@web.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rdunlap@xenotime.net \
    --cc=tilman@imap.cc \
    /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