public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 simplifications
Date: Tue, 11 Jan 2005 15:29:23 +0300	[thread overview]
Message-ID: <41E3C6A3.6070207@yandex.ru> (raw)
In-Reply-To: <1105369990.5698.95.camel@hades.cambridge.redhat.com>

> I prefer to optimise for the common case -- which is the _user_ not the
> developer. The level of verbosity if you enable CONFIG_JFFS2_FS_DEBUG is
> high, but it means that I can take a log from a clueless end-user and
> see precisely what's going on. I can look at a log from someone who's
> having problems, see precisely what's happening, and provide a patch in
> reply. While there are certainly some printks which can go, and even
> more could be demoted to level 2 from level 1 (which is all that's ever
> really useful), I wouldn't want to see it completely stripped of
> debugging output. Not unless you want to take over the task of
> supporting users ;)
>
I have seen once how David have fixed bug after guy just provided the 
debugging output. From this point of view debugging printks are really good.

When developing, the debugging printks are extremely helpful, at least 
for me.


-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

      parent reply	other threads:[~2005-01-11 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 21:18 jffs2 simplifications Jörn Engel
2005-01-08 21:21 ` David Woodhouse
2005-01-10 14:29   ` Jörn Engel
2005-01-09 12:03 ` Artem B. Bityuckiy
2005-01-10 14:51   ` Jörn Engel
2005-01-10 15:13     ` David Woodhouse
2005-01-10 15:58       ` Jörn Engel
2005-01-11 12:29       ` Artem B. Bityuckiy [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=41E3C6A3.6070207@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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