From: David Masover <ninja@slaphack.com>
To: Hubert Chan <hubert@uhoreg.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: The situation at hand and in the future
Date: Mon, 31 May 2004 16:14:25 -0500 [thread overview]
Message-ID: <40BBA031.7090701@slaphack.com> (raw)
In-Reply-To: <87fz9gikco.fsf@uhoreg.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hubert Chan wrote:
[ ... ]
| But without a high-level overview of all the files, and how they all fit
| together, it's still hard to read.
True. Actually, one of the most desirable traits of a hacker is the
ability to take any reference and learn from it as if it were a
tutorial. I know people who can hear me talk about things like
filesystems for a full 5 minutes, and at the end of it come back to me
and say they understood everything, they just need a few definitions
(like what a filesystem is).
But, to make it more accessible to other hackers, someone should
eventually do such a thing. I probably will as I go -- if I read the
reiser4 code this summer, I will post a 'reiser4 cheit sheet' or something.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQLugMHgHNmZLgCUhAQK2yQ//TNnS8k0CMG+redCoGlBstaPlJ53vcL90
9TkrNryd/WqfmdwJo9O79Mqtpc8je23DVeo+4Ti3aKHXZp+R0Fs8FSb/ij/rs2jD
vVfE6bfbSFHne0FCPeucnWad910kHUWcaopgm8nQOu049JbfGFr00XC1kwVwygw+
66RoYwX0Ql0YZbueZhElXY66MOS/EM+X/V6sWvVWLGWWZHgUGFyGXjY3ixudeLMG
cuy7gAkRLyt7VhfI8CT9RD0340RT1XSOmuFClm6gIZ7Oq097U/D5/ArugtvKe7TI
swdcjl+WmiLO9VraW/1x5dXXghZFAxHEUQFtoy6Yjx3Pv7+B5NSx97IP0AdDzSXT
NYErwJAOfHjnaQbUzsTEp7FrpJo8N/QjznfRzhbNqxaD6zF+OgQ0WE7rg7j5hFVr
e/cjQaLGyVWDTzTzHqmWRezPtTQp1pe53jcEA3XiNMk9/56BNyRxHNV1cEw/+jSg
tcbRodCBLrJ7FaNDTuY0/sb4jQ6OOPcz8nTAT51QA76bwI0ruE4Fnp0R8bkYWGbr
D/rpczs7q8qOU7864usAKbyraPtTkcyNc32qf2U8/sHSgxmHEAJwxM3MkZ9wH2ND
D0EdIqUrHT6YPK3r5EwlsO8oKtGQSlJTK0X+wbjniTA/I84/wPj5tA9NAmJp0Aik
EhT5z3D3mcc=
=u0RU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-31 21:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 20:01 The situation at hand and in the future mjt
2004-05-27 21:05 ` Valdis.Kletnieks
2004-05-27 22:09 ` David Masover
2004-05-28 6:33 ` mjt
2004-05-28 19:53 ` Valdis.Kletnieks
2004-05-29 12:48 ` mjt
2004-05-29 14:22 ` David Masover
2004-05-29 15:49 ` mjt
2004-05-29 23:16 ` David Masover
2004-05-30 0:41 ` Hubert Chan
2004-05-30 12:29 ` mjt
2004-05-30 16:54 ` Hubert Chan
2004-05-30 12:27 ` mjt
2004-05-30 17:09 ` Hubert Chan
2004-05-31 0:07 ` The Amazing Dragon
2004-05-30 17:13 ` Hubert Chan
2004-05-30 18:06 ` mjt
2004-05-31 0:45 ` David Masover
2004-05-31 8:38 ` mjt
2004-05-31 15:12 ` David Masover
2004-05-31 17:20 ` Hubert Chan
2004-05-31 21:14 ` David Masover [this message]
2004-05-31 15:16 ` Hubert Chan
2004-06-01 13:25 ` Edward Shushkin
2004-06-02 8:05 ` mjt
2004-06-02 12:51 ` Edward Shushkin
2004-06-02 15:15 ` mjt
2004-05-31 18:31 ` Valdis.Kletnieks
2004-05-31 21:15 ` David Masover
2004-06-02 2:45 ` Hans Reiser
2004-05-29 20:04 ` Hubert Chan
2004-05-29 23:19 ` David Masover
2004-05-31 18:27 ` Valdis.Kletnieks
2004-05-31 21:23 ` David Masover
2004-06-01 2:09 ` Hubert Chan
2004-06-05 4:50 ` David Masover
2004-06-05 7:30 ` Valdis.Kletnieks
2004-06-05 10:07 ` Christian Iversen
2004-06-07 17:35 ` Valdis.Kletnieks
2004-06-09 22:01 ` David Masover
2004-06-10 8:23 ` mjt
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=40BBA031.7090701@slaphack.com \
--to=ninja@slaphack.com \
--cc=hubert@uhoreg.ca \
--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.