From: Ben Elliston <bje@redhat.com>
To: cgen@sources.redhat.com
Subject: Cosmetic change
Date: Wed, 04 Jul 2001 00:24:00 -0000 [thread overview]
Message-ID: <15170.48466.662465.739136@scooby.brisbane.redhat.com> (raw)
I've just committed the following change:
2001-07-04 Ben Elliston <bje@redhat.com>
* read.scm (include): Log "Including file" message at level 1,
rather than outputting it with (display).
(cpu-load): Log "Loading cpu description" and "Processing cpu
description" messages at levels 1 and 2, respectively, rather than
using (display).
This makes logging of user messages more uniform, through the (logit)
function. It also has the nice side effect of logging these somewhat
uninformative messages at level 1, whereby more optimistic users can
skip them and enjoy a quiter run.
Ben
reply other threads:[~2001-07-04 0:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15170.48466.662465.739136@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).