From: Stan Shebs <shebs@cygnus.com>
To: jtc@redbacknetworks.com
Cc: gdb@cygnus.com, law@cygnus.com
Subject: Re: Conditionals in GDB manual
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199902052040.MAA09998@andros.cygnus.com> (raw)
In-Reply-To: <5mg18kobd5.fsf@jtc.redbacknetworks.com>
From: jtc@redbacknetworks.com (J.T. Conklin)
Date: 05 Feb 1999 12:15:50 -0800
Ideally, there would be One True GDB Manual that contained all
information for all hosts and targets, organized in such a way so
environment specific information could be identified and located
easily by readers. Appendicies for both host and target specific
information might be a good way to accomplish this.
Yes. The effect of the conditionals is to allow people to make 2^40
different One of Many GDB Manuals, each with no indication to the
reader that they are different from the complete manual.
The many conditionals that select parts of the "Remote Debugging"
chapter seem to go along with this idea, although the individual
sections don't share the same outline of sub-sections and moving
them to an appendix might be a bit more of an overhaul than is
envisioned.
There's no reason not to reorganize the manual in whatever way makes
it the most accessible to readers. I note that most of GCC's target
specific info sits in the chapter on command-line options, and
everybody seems to be OK with that. For GDB, I'm leaning towards a
regular chapter or two, mostly because the info for some targets is
fairly extensive and critical to using them, and appendices are better
for small amounts of optional info. But I haven't made a decision yet.
Stan
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199902050402.UAA16377@cygint.cygnus.com>
1999-04-01 0:00 ` Jeffrey A Law
1999-04-01 0:00 ` J.T. Conklin
1999-04-01 0:00 ` Stan Shebs [this message]
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 Stan Shebs
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=199902052040.MAA09998@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb@cygnus.com \
--cc=jtc@redbacknetworks.com \
--cc=law@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