public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Luke A. Guest" <laguest@abyss2.demon.co.uk>
To: Laurent GUERBY <laurent@guerby.net>
Cc: GCC ML <gcc@gcc.gnu.org>
Subject: Re: Status of the GNAT Ada compiler
Date: Sat, 27 Nov 2004 01:48:00 -0000	[thread overview]
Message-ID: <1101518111.26204.65.camel@rogue.abyss2.demon.co.uk> (raw)
In-Reply-To: <1101517308.26196.58.camel@rogue.abyss2.demon.co.uk>

Well, it seems my gnat needs to be at the start of my PATH, which I keep forgetting ;-)

But it still doesn't make what I said earlier any less relevant :-D

Luke.


      parent reply	other threads:[~2004-11-27  1:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  0:44 Luke A. Guest
2004-11-27  0:56 ` Andrew Pinski
2004-11-27  1:01   ` Luke A. Guest
2004-11-27  1:13 ` Laurent GUERBY
2004-11-27  1:15   ` Luke A. Guest
2004-11-27  1:41     ` Laurent GUERBY
2004-11-27  1:48     ` Luke A. Guest [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=1101518111.26204.65.camel@rogue.abyss2.demon.co.uk \
    --to=laguest@abyss2.demon.co.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=laurent@guerby.net \
    /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).