From: David Masover <ninja@slaphack.com>
To: David Dabbs <david@dabbs.net>
Cc: reiser@namesys.com, gbeshers@comcast.net, reiserfs-list@namesys.com
Subject: Re: viewprinting: what format should views be stored in?
Date: Wed, 18 Aug 2004 13:37:38 -0500 [thread overview]
Message-ID: <4123A1F2.1010001@slaphack.com> (raw)
In-Reply-To: <20040818075216.B920D15DBC@mail03.powweb.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Dabbs wrote:
| If you only have three months to prove a concept and obtain continued
| funding, then I agree with Hans's preference for reusing as much
| existing work as possible. Adapting Hans's statement regarding
I've also been lurking and not reading too much, but here's my thought:
It is far more important to create code which can easily be re-used in
the future than to re-use code that you have now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQSOh8ngHNmZLgCUhAQKGGBAAhIOpJGCU2qcknOIjJ1qUdYEVOoqUIi8R
85G4WzVbJm/q73N/gaIhvyYfpRz6dvLdcfLoLkg2NbYcOfL7g54TrmKzEF6wsbQb
9SVE6zkrffqlclDUV7vkaIv1ZtipMDhbpWqLXM0UNiGvyNq1ltVazOQxdI9ptmC6
f9xj/EkwWT35PDddTLk8pEp0wa1D3WhBc+IjFPKplSD/eoHwfypAU/Hfbcrj80F7
wNdgEv9/kYUcgRqCoZcCoEODoBgiol5hcbVg44RdAyQVUhqJHV0rOqmZJ3llLQBR
EEnoqLTdPgmF8OnZUJ6GRfgKIeQsXy0OQ4Dl4r8YbxbanAaUSdMEacKclgyY7GeX
Y72/XiEr6WR4SumdckgHdTkMlwxJPndUeUC4L2f/ZpK+f7A3PAU6IjguxSy7vHU7
2LffTf8xkGegR9hwlgDwRFuyyZTaYqRqU/5h04lheUFhu5E43gI/N3NsR9+gkDdc
IXEW1n+UCMgUrxLW+9VnvujOruDHDkrjDUgEBENBQOmksJfq1nc6o48jbWtOjnVD
Wp1nD6CIGdcmGLXIXhKXZYwLKNrrGFVPd9xwQRjmuTU0DtoYBCA7t6ezyhzGcQYs
UtEtGaDJXiiYZCL9sXwjrwx3Pag06Zc12icqlPSfddiSufQeesokEG7hiD2kP2G0
2SURGS8gjhs=
=AXNc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-18 18:37 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 7:52 viewprinting: what format should views be stored in? David Dabbs
2004-08-18 18:37 ` David Masover [this message]
2004-08-18 21:47 ` George Beshers
2004-08-18 19:20 ` George Beshers
2004-08-18 20:20 ` Hans Reiser
2004-08-18 21:44 ` George Beshers
2004-08-18 21:48 ` Hans Reiser
2004-08-18 23:18 ` George Beshers
2004-08-19 0:42 ` Hans Reiser
2004-08-19 2:01 ` George Beshers
2004-08-19 5:50 ` Hans Reiser
2004-08-19 12:48 ` George Beshers
2004-08-20 6:59 ` Hans Reiser
2004-08-20 12:36 ` George Beshers
2004-08-20 18:14 ` Hans Reiser
2004-08-20 21:42 ` George Beshers
2004-08-18 19:34 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2004-08-22 5:45 David Dabbs
2004-08-21 20:48 David Dabbs
2004-08-21 7:38 David Dabbs
2004-08-21 8:59 ` Hans Reiser
2004-08-20 22:29 David Dabbs
2004-08-20 17:14 David Dabbs
2004-08-20 7:23 David Dabbs
2004-08-20 16:10 ` Valdis.Kletnieks
2004-08-20 21:04 ` George Beshers
2004-08-21 6:42 ` Hans Reiser
2004-08-19 7:40 David Dabbs
2004-08-19 11:21 ` David Greaves
2004-08-19 16:16 ` George Beshers
2004-08-20 6:19 ` Hans Reiser
2004-10-26 14:45 ` Lamont R. Peterson
2004-10-26 16:39 ` Hans Reiser
2004-10-26 16:57 ` George Beshers
2004-10-26 18:37 ` Hans Reiser
2004-10-26 20:20 ` George Beshers
2004-10-27 4:48 ` Hans Reiser
[not found] ` <4124D09A.1060208@comcast.net>
2004-08-19 17:31 ` David Greaves
2004-08-20 6:52 ` Hans Reiser
2004-08-20 12:08 ` George Beshers
2004-08-20 14:07 ` David Greaves
2004-10-26 15:54 ` Lamont R. Peterson
2004-10-27 1:04 ` David Masover
2004-08-20 6:13 ` Hans Reiser
2004-08-19 14:30 ` George Beshers
2004-08-16 0:15 Hans Reiser
2004-08-16 1:48 ` George Beshers
2004-08-16 2:02 ` Hans Reiser
2004-08-16 13:47 ` George Beshers
2004-08-16 19:50 ` George Beshers
2004-08-17 7:07 ` Hans Reiser
2004-08-17 19:29 ` George Beshers
2004-08-17 20:28 ` Hans Reiser
2004-08-17 23:46 ` George Beshers
2004-08-18 2:22 ` Hans Reiser
[not found] ` <4121F4D6.8090506@comcast.net>
2004-08-17 19:43 ` Hans Reiser
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=4123A1F2.1010001@slaphack.com \
--to=ninja@slaphack.com \
--cc=david@dabbs.net \
--cc=gbeshers@comcast.net \
--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.