From: Tim Goodwin <tjg@star.le.ac.uk>
To: callum.gibson@db.com
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: found a problem, sorry
Date: Tue, 25 Jun 2002 11:32:50 -0500 [thread overview]
Message-ID: <20020625153250.31276.qmail@happy.star.le.ac.uk> (raw)
In-Reply-To: <20020621000930.48466.qmail@merton.aus.deuba.com> (callum.gibson@db.com)
> I wish I'd seen this before the release but I haven't been testing them
> religiously. Both 1.6c6 and 1.7 hang in make trip in the current directory
> globbing on Solaris 2.6 - truss output shows:
It's not as serious as you think; rc makes and trips fine on at least one
Solaris 2.6 box that I have here.
Suggest we take this off the list till we get to the bottom of it.
Can you send me the output of `showrev -p' on your failing 2.6 box?
Also, are you building on a local filesystem, or NFS, etc?
> Does anyone know if there are mailing list archives stored anywhere? There's
> no link from the rc home page but I think I've come across it before.
There's a couple of list archive files in
ftp://ftp.sys.utoronto.ca/pub/rc/
but it only seems to go up to January 2001.
Tim.
prev parent reply other threads:[~2002-06-27 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 1:09 callum.gibson
2002-06-25 16:32 ` Tim Goodwin [this message]
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=20020625153250.31276.qmail@happy.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=callum.gibson@db.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).