From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Manuel Krause <manuelkrause@netscape.net>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: BTW: 2.4.19-patches-to-come?
Date: 08 May 2002 09:04:50 -0400 [thread overview]
Message-ID: <1020863090.32044.202.camel@tiny> (raw)
In-Reply-To: <20020508093044.A32071@namesys.com>
On Wed, 2002-05-08 at 01:30, Oleg Drokin wrote:
> > I don't find this information very explicative. And I really don't know
> > enough about reiserfs code to interprete these lines. BTW, can we have a
> > "ReiserFS: " in front of these messages?
>
> In fact I think these messages should not be printed at all, there is no
> useful information given to the user.
I like a summary line: completed X number of truncates and N number of
deletes.
-chris
next prev parent reply other threads:[~2002-05-08 13:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:15 BTW: 2.4.19-patches-to-come? Manuel Krause
2002-05-07 5:22 ` Oleg Drokin
2002-05-07 14:02 ` Yury Yu. Rupasov
2002-05-07 19:35 ` Manuel Krause
2002-05-08 5:30 ` Oleg Drokin
2002-05-08 13:04 ` Chris Mason [this message]
2002-05-08 13:08 ` Oleg Drokin
2002-05-08 13:16 ` Chris Mason
2002-05-08 13:20 ` Oleg Drokin
2002-05-08 13:34 ` Chris Mason
2002-05-17 1:49 ` Manuel Krause
2002-05-17 4:56 ` Oleg Drokin
2002-05-17 9:47 ` Pierre Etchemaite
2002-05-17 9:47 ` Oleg Drokin
2002-05-07 13:52 ` Yury Yu. Rupasov
2002-05-07 20:41 ` Manuel Krause
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 15:36 Dieter Nützel
2002-05-17 15:47 ` Chris Mason
2002-05-17 18:20 ` Dieter Nützel
2002-05-17 18:26 ` Dieter Nützel
2002-05-17 15:54 ` Oleg Drokin
2002-05-17 17:05 ` Dieter Nützel
2002-05-17 18:28 ` Oleg Drokin
2002-05-17 19:44 ` Dieter Nützel
2002-05-18 5:44 ` Oleg Drokin
2002-05-18 13:18 ` Dieter Nützel
2002-05-18 16:29 ` Oleg Drokin
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=1020863090.32044.202.camel@tiny \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=manuelkrause@netscape.net \
--cc=reiserfs-list@namesys.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 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.