Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] doc/gdbint.texinfo: remove references to pyramid macros
Date: Tue, 09 Apr 2002 09:40:00 -0000	[thread overview]
Message-ID: <200204091640.g39Ge8F12926@duracef.shout.net> (raw)

And now for something different.  I found this in an old
"work in progress" directory.

Here's a doco cleanup patchlet.  This removes references to
PYRAMID_* from gdbint.texinfo, section "Obsolete Conditionals".

Here is the history:

  gdb HEAD  		no reference to PYRAMID_*
  gdb gdb_5_2-branch	no reference to PYRAMID_*
  gdb 5.1.1		no reference to PYRAMID_*
  gdb 5.1		no reference to PYRAMID_*
  gdb 5.0		all references to PYRAMID_* are "OBSOLETE"
  gdb 4.18		PYRAMID_* is live

I would like to apply this to HEAD.  It would not hurt the 5.2 branch,
but it's not necessary, either.

Okay to apply?

Michael C

===

2002-04-09  Michael Chastain  <mec@shout.net>

	* gdb.texinfo (Obsolete Conditionals): Remove references to
	pyramid macros.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.72
diff -c -3 -p -r1.72 gdbint.texinfo
*** gdbint.texinfo	6 Apr 2002 00:02:52 -0000	1.72
--- gdbint.texinfo	9 Apr 2002 16:36:54 -0000
*************** and deleted from all of @value{GDBN}'s c
*** 5728,5740 ****
  Any @file{@var{foo}-xdep.c} file that references STACK_END_ADDR
  is so old that it has never been converted to use BFD.  Now that's old!
  
- @item PYRAMID_CONTROL_FRAME_DEBUGGING
- pyr-xdep.c
- @item PYRAMID_CORE
- pyr-xdep.c
- @item PYRAMID_PTRACE
- pyr-xdep.c
- 
  @item REG_STACK_SEGMENT
  exec.c
  
--- 5728,5733 ----


             reply	other threads:[~2002-04-09 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  9:40 Michael Elizabeth Chastain [this message]
2002-04-09 11:14 ` Eli Zaretskii
2002-04-09 11:38 Michael Elizabeth Chastain
2002-04-09 22:06 ` Eli Zaretskii
2002-04-09 22:12 Michael Elizabeth Chastain

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=200204091640.g39Ge8F12926@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.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