From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: reiserfsprogs release
Date: Sat, 20 Jul 2002 22:50:15 -0400 [thread overview]
Message-ID: <87bs91ssk8.fsf@labatt.uhoreg.ca> (raw)
In-Reply-To: 200207101206.48370.vitaly@namesys.com
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
>>>>> "Vitaly" =3D=3D Vitaly Fertman <vitaly@namesys.com> writes:
Vitaly> Hi all, the latest reiserfsprogs-3.6.2 is available on our ftp
Vitaly> site. ...
The web site (http://namesys.com/download.html) still claims that 3.x.1b
is the latest.
BTW, the second box from the top on the left (re: don't compile with GCC
2.96) has yellow text on a white background for me - Mozilla 1.0. Aha!
The bgcolor for that table cell is missing the # in front of the colour
code, so Mozilla doesn't understand the colour.
=2D-=20
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2002-07-21 2:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 14:29 reiserfsprogs release Vitaly Fertman
2002-06-25 16:52 ` Dirk Mueller
2002-06-26 9:17 ` Vitaly Fertman
2002-07-10 8:06 ` Vitaly Fertman
2002-07-10 9:10 ` Brandon Low
2002-07-10 9:02 ` Vitaly Fertman
2002-07-10 14:23 ` Steven Cole
2002-07-10 14:31 ` [reiserfs-list] " Oleg Drokin
2002-07-10 14:31 ` Oleg Drokin
2002-07-10 14:38 ` Christoph Hellwig
2002-07-10 14:44 ` Chris Mason
2002-07-10 14:46 ` Christoph Hellwig
2002-07-10 14:47 ` [reiserfs-list] " Oleg Drokin
2002-07-10 14:47 ` Oleg Drokin
2002-07-11 2:27 ` Matthias Andree
2002-07-21 2:50 ` Hubert Chan [this message]
2002-07-21 18:32 ` Hubert Chan
2002-07-22 6:57 ` Oleg Drokin
2002-08-12 10:42 ` Vitaly Fertman
2002-08-12 12:09 ` Alan Cox
2002-08-12 11:00 ` Vitaly Fertman
2002-06-26 17:37 Dieter Nützel
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=87bs91ssk8.fsf@labatt.uhoreg.ca \
--to=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.