From: Ben Elliston <bje@redhat.com>
To: bemis <bemis@iol.unh.edu>
Cc: sid@sources.redhat.com
Subject: Re: SID compilation FAIL on alphaev56
Date: Wed, 13 Nov 2002 23:05:00 -0000 [thread overview]
Message-ID: <m3znscfx83.fsf@scooby.brisbane.redhat.com> (raw)
In-Reply-To: bemis's message of "Wed, 13 Nov 2002 16:21:10 -0400"
>>>>> "bemis" == bemis <bemis@iol.unh.edu> writes:
bemis> I did post this to the sid mailing list, but All I got a few
bemis> days later was a sid cvs snapshot. Our sid package has a cvs
bemis> snapshot of 2002-10-28. I'll check if there is a later
bemis> version.
I'm sure there will be. Alternatively, you can check it straight out
of CVS to be sure you've got the latest version.
Cheers, Ben
next prev parent reply other threads:[~2002-11-14 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DD2A669.87669C32@iol.unh.edu>
2002-11-13 11:59 ` Ben Elliston
2002-11-13 12:21 ` bemis
2002-11-13 23:05 ` Ben Elliston [this message]
2002-11-13 12:44 ` Frank Ch. Eigler
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=m3znscfx83.fsf@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=bemis@iol.unh.edu \
--cc=sid@sources.redhat.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 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).