From: Stan Shebs <shebs@cygnus.com>
To: law@cygnus.com
Cc: gdb@cygnus.com
Subject: Re: Conditionals in GDB manual
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199902051951.LAA05380@andros.cygnus.com> (raw)
In-Reply-To: <16950.918232591@hurl.cygnus.com>
Date: Fri, 05 Feb 1999 09:36:31 -0700
From: Jeffrey A Law <law@hurl.cygnus.com>
Might it make more sense to have processor specific appendices? We need
somewhere to put processor/os specific stuff.
Yes, I'd like to do that anyway. There have been two different attempts
to organize platform-specific stuff, each incomplete. I think readers
just flip over those sections now, so I don't think their presence is
objectionable, but it is hard to find, say, all remote debugging details
or all native debugging details.
Right now the conditionals are making it hard even to figure out what
the organization should be, since there are so many (about 280
ifset/ifclears in the 11K lines of gdb.texinfo). Makes the manual
look like an over-ifdefed piece of source code...
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
1999-04-01 0:00 ` Stan Shebs [this message]
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=199902051951.LAA05380@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb@cygnus.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