Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: dj@redhat.com, eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: [patch/djgpp] add lines for new files to fnchange.lst
Date: Sun, 19 Oct 2003 14:39:00 -0000	[thread overview]
Message-ID: <200310191438.h9JEcqDY005339@duracef.shout.net> (raw)

This patch adds some lines to fnchange.lst for some recent files.
I found these by checking the ARI.

By the way, none of these were lines that I removed yesterday.
The ARI says that my patch yesterday was okay.

Testing: I have not tested this, but I proofread it carefully.
It will get tested by the nightly ARI run.

I am committing this as obvious.

Michael C

===

2003-10-19  Michael Chastain <mec@shout.net>

	* config/djgpp/fnchange.lst: Add lines for:
	gdb/amd64nbsd-nat.c, gdb/amd64nbsd-tdep.c,
	gdb/i386fbsd-nat.c, gdb/i386fbsd-tdep.c,
	gdb/sparc64fbsd-nat.c, gdb/sparc64bsd-tdep.c.

Index: fnchange.lst
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/fnchange.lst,v
retrieving revision 1.60
diff -c -3 -p -r1.60 fnchange.lst
*** fnchange.lst	18 Oct 2003 14:36:16 -0000	1.60
--- fnchange.lst	19 Oct 2003 14:27:22 -0000
***************
*** 62,69 ****
  @V@/gdb/ChangeLog-2002 @V@/gdb/ChangeLog.002
  @V@/gdb/ChangeLog-3.x @V@/gdb/ChangeLog.3-x
  @V@/gdb/ada-exp.tab.c @V@/gdb/ada-exp_tab.c
- @V@/gdb/amd64fbsd-tdep.c @V@/gdb/a64fb-tdep.c
  @V@/gdb/amd64fbsd-nat.c @V@/gdb/a64fb-nat.c
  @V@/gdb/alphabsd-nat.c @V@/gdb/alphb-nat.c
  @V@/gdb/alphabsd-tdep.c @V@/gdb/alphb-tdep.c
  @V@/gdb/alphanbsd-tdep.c @V@/gdb/alphnb-tdep.c
--- 62,71 ----
  @V@/gdb/ChangeLog-2002 @V@/gdb/ChangeLog.002
  @V@/gdb/ChangeLog-3.x @V@/gdb/ChangeLog.3-x
  @V@/gdb/ada-exp.tab.c @V@/gdb/ada-exp_tab.c
  @V@/gdb/amd64fbsd-nat.c @V@/gdb/a64fb-nat.c
+ @V@/gdb/amd64fbsd-tdep.c @V@/gdb/a64fb-tdep.c
+ @V@/gdb/amd64nbsd-nat.c @V@/gdb/a64nb-nat.c
+ @V@/gdb/amd64nbsd-tdep.c @V@/gdb/a64nb-tdep.c
  @V@/gdb/alphabsd-nat.c @V@/gdb/alphb-nat.c
  @V@/gdb/alphabsd-tdep.c @V@/gdb/alphb-tdep.c
  @V@/gdb/alphanbsd-tdep.c @V@/gdb/alphnb-tdep.c
***************
*** 109,114 ****
--- 111,118 ----
  @V@/gdb/i386-linux-tdep.c @V@/gdb/i386linux-tdep.c
  @V@/gdb/i386bsd-nat.c @V@/gdb/i3bsd-nat.c
  @V@/gdb/i386bsd-tdep.c @V@/gdb/i3bsd-tdep.c
+ @V@/gdb/i386fbsd-nat.c @V@/gdb/i3fbsd-nat.c
+ @V@/gdb/i386fbsd-tdep.c @V@/gdb/i3fbsd-tdep.c
  @V@/gdb/i386gnu-nat.c @V@/gdb/i3gnu-nat.c
  @V@/gdb/i386gnu-tdep.c @V@/gdb/i3gnu-tdep.c
  @V@/gdb/i386nbsd-nat.c @V@/gdb/i3nbsd-nat.c
***************
*** 149,154 ****
--- 153,160 ----
  @V@/gdb/remote-vx68.c @V@/gdb/rmt-vx68.c
  @V@/gdb/remote-vxmips.c @V@/gdb/rmt-vxmips.c
  @V@/gdb/remote-vxsparc.c @V@/gdb/rmt-vxsparc.c
+ @V@/gdb/sparc64fbsd-nat.c @V@/gdb/sp64fb-nat.c
+ @V@/gdb/sparc64fbsd-tdep.c @V@/gdb/sp64fb-tdep.c
  @V@/gdb/sparcnbsd-nat.c @V@/gdb/spnb-nat.c
  @V@/gdb/sparcnbsd-tdep.c @V@/gdb/spnb-tdep.c
  @V@/gdb/testsuite/.gdbinit @V@/gdb/testsuite/gdb.ini


             reply	other threads:[~2003-10-19 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 14:39 Michael Elizabeth Chastain [this message]
2003-10-19 16:35 ` Eli Zaretskii

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=200310191438.h9JEcqDY005339@duracef.shout.net \
    --to=mec@shout.net \
    --cc=dj@redhat.com \
    --cc=eliz@gnu.org \
    --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