From: "Thomas D. Ward" <slingshooter@valkyrie.net>
To: <speakup@braille.uwo.ca>
Subject: Re: RH 7.4 beta?
Date: Tue, 24 Sep 2002 22:05:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0209242201440.16084-100000@localhost.localdomain> (raw)
In-Reply-To: <20020924164302.29976.26495.Mailman@speech.braille.uwo.ca>
Hi, Bill. Thanks for the info. Actually, someone told me it was 7.4, but
after looking at the ftp site I see it is 8.0. Thanks for the correction,
and tips.
I guess I can wait a week or two for the full version if it is that close.
It looks like many mirrors hve just added a 8.0 branch, and as you say it
usually doesn't take long after the branch appears before it actually gets
contents.
next parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020924164302.29976.26495.Mailman@speech.braille.uwo.ca>
` Thomas D. Ward [this message]
` Aaron Howell
[not found] <20020924010201.12446.42260.Mailman@speech.braille.uwo.ca>
` Thomas Ward
` Aaron Howell
` Darragh
` Aaron Howell
` Sunfire
` William F. Acker WB2FLW +1-303-777-8123
` Sunfire
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=Pine.LNX.4.33.0209242201440.16084-100000@localhost.localdomain \
--to=slingshooter@valkyrie.net \
--cc=speakup@braille.uwo.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).