From: David B Harris <david@eelf.ddts.net>
To: Hans Reiser <reiser@namesys.com>
Cc: mason <mason@namesys.com>,
reiserfs mailing list <reiserfs-list@namesys.com>,
Debian Development <debian-devel@lists.debian.org>
Subject: Re: new credit printing mechanism now present in reiserfsprogs
Date: Wed, 23 Jul 2003 04:15:53 -0400 [thread overview]
Message-ID: <20030723041553.791f4115.david@eelf.ddts.net> (raw)
In-Reply-To: <3F1E3D05.3090309@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
(That's a really long recipient list - does this need only go to
reiserfs-list@namesys.com and debian-devel@lists.debian.org?)
On Wed, 23 Jul 2003 11:45:09 +0400
Hans Reiser <reiser@namesys.com> wrote:
> it now prints two random credits rather than all of them, and credits
> for the developers are in place. suggestions about how to improve this
> while preserving the credits (e.g. printing them at a different stage of
> mkreiserfs, etc.) are welcome.
If mkreiserfs was slower, I would suggest printing them at the start of
the program. It gives people something to read while they're waiting for
it to finish. (They would probably be more likely to read it, too.)
It takes less than 4 seconds on a regular file of 410M here, though, so
that's not a whole lot of time. Does it take longer on bigger
filesystems? Lots of people are making many-gigabyte filesystems these
days, so perhaps that really is a good idea.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-23 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 7:45 new credit printing mechanism now present in reiserfsprogs Hans Reiser
2003-07-23 8:15 ` David B Harris [this message]
2003-07-23 8:40 ` Yury Umanets
2003-07-23 9:01 ` Hans Reiser
2003-07-23 9:08 ` Yury Umanets
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=20030723041553.791f4115.david@eelf.ddts.net \
--to=david@eelf.ddts.net \
--cc=debian-devel@lists.debian.org \
--cc=mason@namesys.com \
--cc=reiser@namesys.com \
--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.