public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Janis Johnson <janis187@us.ibm.com>
Cc: David Edelsohn <dje@watson.ibm.com>,
	Joe Buck <jbuck@synopsys.com>, <gcc@gcc.gnu.org>
Subject: Re: build status page problem
Date: Mon, 10 Dec 2001 03:56:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.43.0112101156590.4794-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20011209123440.A11359@us.ibm.com>

On Sun, 9 Dec 2001, Janis Johnson wrote:
> Here's how I'd like to change the Final Installation documentation for
> the mainline, with similar changes to 3.0, hopefully in time for the
> 3.0.3 release.

This looks fine (for both branches) with minor changes:

> --- gcc/doc/install.texi.orig	Sun Dec  9 12:13:19 2001
> +++ gcc/doc/install.texi	Sun Dec  9 12:13:32 2001
> +Output from running @file{@var{srcdir}/config.guess}.  (Do
>  not send us the @file{config.guess} file itself, just the one-line output from
> -running it!)  Also specify which version you built.

I'd write "Do not send us that file itself..." (even though it has been
the other way already before your patch)".

> +The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
> +this is available from @file{/etc/issue}.

"...these/this should be available..." (as we cannot be sure about all
systems).

Thanks!

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

      reply	other threads:[~2001-12-10 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 10:01 Joe Buck
2001-12-05 10:17 ` Janis Johnson
2001-12-05 10:22   ` Joe Buck
2001-12-05 10:22   ` David Edelsohn
2001-12-05 10:52     ` Janis Johnson
2001-12-09 12:52     ` Janis Johnson
2001-12-10  3:56       ` Gerald Pfeifer [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=Pine.BSF.4.43.0112101156590.4794-100000@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=jbuck@synopsys.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).