From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Dave Love <d.love@dl.ac.uk>
Cc: egcs@cygnus.com
Subject: Re: new test will hang 'make check-g77'
Date: Thu, 12 Mar 1998 14:50:00 -0000 [thread overview]
Message-ID: <9803122235.AA10852@moene.indiv.nluug.nl> (raw)
In-Reply-To: <rzq3egnzosc.fsf@djlvig.dl.ac.uk>
Craig> BTW, I've been assuming I should submit these to Jeff Law for
Craig> actual installation via CVS, but, perhaps, Robert Lipe, you'd
Craig> be willing to do this
Well, there's the assumption that, once you have your network up,
you should switch to CVS and take over the Fortran related part of
committing changes ...
> Wouldn't it be a better use of resources if I or Toon
> did this, since we're likely familiar with the bugs, and
> have Robert's time & expertise devoted to something else
> (not that I particularly need work and am obviously
> grateful for it being done one way or another)? Or is
> it actually better if someone else does it?
I certainly think that's a better use of Robert's time. However,
as I can't run dejagnu on m68k-next-nextstep3, I need to do some
hand-fixing of sources before I can compile them.
And, on another thread:
Robert> I hate to admit this in this crowd, but I don't do emacs.
> At least you recognise it :-)
Dave probably knows how to get out of it (control-z, kill %1
doesn't work over here).
Cheers,
Toon.
next prev parent reply other threads:[~1998-03-12 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-10 22:15 Robert Lipe
1998-03-11 9:04 ` Dave Love
1998-03-11 12:08 ` Robert Lipe
1998-03-11 15:53 ` Dave Love
1998-03-11 15:53 ` Robert Lipe
1998-03-12 8:07 ` Craig Burley
1998-03-12 11:34 ` Dave Love
1998-03-12 14:50 ` Toon Moene [this message]
1998-03-16 20:25 ` Adding g77 test cases to egcs Craig Burley
1998-03-12 12:44 ` new test will hang 'make check-g77' Dave Love
1998-03-11 9:39 ` Craig Burley
1998-03-11 9:39 ` Robert Lipe
1998-03-11 15:53 ` Craig Burley
1998-03-11 12:08 ` Robert Lipe
1998-03-11 17:54 ` Joe Buck
1998-03-12 10:40 Kate Hedstrom
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=9803122235.AA10852@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=d.love@dl.ac.uk \
--cc=egcs@cygnus.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).