From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer),
psycho@albatross.co.nz, oliva@dcc.unicamp.br, cat@zip.com.au,
egcs@egcs.cygnus.com
Subject: Re: (Getting rid of) man pages
Date: Fri, 23 Apr 1999 01:52:00 -0000 [thread overview]
Message-ID: <vyzzp3zsoxd.fsf@issan.cs.uni-dortmund.de> (raw)
In-Reply-To: <199904222341.QAA13973@atrus.synopsys.com>
Joe Buck <jbuck@Synopsys.COM> writes:
|> The key is to define the purpose of man pages. They are not complete
|> documentation, the gcc manual is. Rather, they should be a quick
|> reference, describing how to invoke gcc, giving the meaning of the flags,
|> and pointing the user to the gcc manual for further details.
That's what info gcc 'invoking gcc' is for. With the current texinfo
snapshot you can even say info --show-options gcc.
--
Andreas Schwab "And now for something
schwab@issan.cs.uni-dortmund.de completely different"
schwab@gnu.org
WARNING: multiple messages have this Message-ID
From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: pfeifer@dbai.tuwien.ac dot@(Gerald Pfeifer),
psycho@albatross.co.nz, oliva@dcc.unicamp.br, cat@zip.com.au,
egcs@egcs.cygnus.com
Subject: Re: (Getting rid of) man pages
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <vyzzp3zsoxd.fsf@issan.cs.uni-dortmund.de> (raw)
Message-ID: <19990430231500.kz8wkGMVf8JeapN97p9ByOlVK2La4IbRxUF7WdajK8c@z> (raw)
In-Reply-To: <199904222341.QAA13973@atrus.synopsys.com>
Joe Buck <jbuck@Synopsys.COM> writes:
|> The key is to define the purpose of man pages. They are not complete
|> documentation, the gcc manual is. Rather, they should be a quick
|> reference, describing how to invoke gcc, giving the meaning of the flags,
|> and pointing the user to the gcc manual for further details.
That's what info gcc 'invoking gcc' is for. With the current texinfo
snapshot you can even say info --show-options gcc.
--
Andreas Schwab "And now for something
schwab@issan.cs.uni-dortmund.de completely different"
schwab@gnu.org
next prev parent reply other threads:[~1999-04-23 1:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-22 9:23 Gerald Pfeifer
1999-04-22 9:35 ` Alexandre Oliva
1999-04-30 23:15 ` Alexandre Oliva
1999-04-22 9:52 ` CaT
1999-04-22 10:08 ` Alexandre Oliva
1999-04-22 10:22 ` CaT
1999-04-30 23:15 ` CaT
1999-04-22 10:23 ` Keith Duthie
1999-04-22 10:26 ` CaT
1999-04-30 23:15 ` CaT
1999-04-22 10:31 ` Alexandre Oliva
1999-04-30 23:15 ` Alexandre Oliva
1999-04-22 16:10 ` Gerald Pfeifer
1999-04-22 16:44 ` Joe Buck
1999-04-22 22:19 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-23 1:52 ` Andreas Schwab [this message]
1999-04-23 9:12 ` Joe Buck
1999-04-24 0:31 ` rich-paul
1999-04-24 0:50 ` CaT
1999-04-30 23:15 ` CaT
1999-04-24 5:50 ` craig
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` rich-paul
1999-04-30 23:15 ` Joe Buck
1999-04-23 10:52 ` Marc Espie
1999-04-23 11:00 ` Joe Buck
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Marc Espie
1999-04-30 23:15 ` Andreas Schwab
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Gerald Pfeifer
1999-04-30 23:15 ` Keith Duthie
1999-04-30 23:15 ` Alexandre Oliva
1999-04-30 23:15 ` CaT
1999-04-30 23:15 ` Gerald Pfeifer
1999-06-25 6:25 ` Alexandre Oliva
1999-06-30 15:43 ` Alexandre Oliva
1999-04-23 11:10 Josh Stern
1999-04-30 23:15 ` Josh Stern
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=vyzzp3zsoxd.fsf@issan.cs.uni-dortmund.de \
--to=schwab@issan.cs.uni-dortmund.de \
--cc=cat@zip.com.au \
--cc=egcs@egcs.cygnus.com \
--cc=jbuck@Synopsys.COM \
--cc=oliva@dcc.unicamp.br \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=psycho@albatross.co.nz \
/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).