From: Richard Earnshaw <rearnsha@arm.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: ARI and DUP filenames
Date: Tue, 19 Feb 2002 11:31:00 -0000 [thread overview]
Message-ID: <200202191928.TAA07094@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 19 Feb 2002 21:19:03 +0200." <5402-Tue19Feb2002211902+0200-eliz@is.elta.co.il>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
> You don't need to do anything beyond updating fnchange.lst. One
> request: when you invent the 8+3-clean names, please look how similar
> names are dealt with on fnchange.lst, and do something along the same
> lines. TIA
Ok, committed the following:
2002-02-19 Richard Earnshaw <rearnsha@arm.com>
* config/djgpp/fnchange.lst: Add change rules for armnbsd-tdep.c and
armnbsd-nat.c.
[-- Attachment #2: gdb-fnlist.patch --]
[-- Type: text/x-patch , Size: 737 bytes --]
Index: fnchange.lst
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/fnchange.lst,v
retrieving revision 1.23
diff -p -r1.23 fnchange.lst
*** fnchange.lst 2002/01/20 03:28:59 1.23
--- fnchange.lst 2002/02/19 19:24:35
***************
*** 53,58 ****
--- 53,60 ----
@V@/gdb/ChangeLog-3.x @V@/gdb/ChangeLog.3-x
@V@/gdb/arm-linux-nat.c @V@/gdb/armlin-nat.c
@V@/gdb/arm-linux-tdep.c @V@/gdb/armlin-tdep.c
+ @V@/gdb/armnbsd-nat.c @V@/gdb/armnbd-nat.c
+ @V@/gdb/armnbsd-tdep.c @V@/gdb/armnbd-tdep.c
@V@/gdb/c-exp.tab.c @V@/gdb/c-exp_tab.c
@V@/gdb/config/alpha/alpha-osf1.mh @V@/gdb/config/alpha/alphosf1.mh
@V@/gdb/config/alpha/alpha-osf2.mh @V@/gdb/config/alpha/alphosf2.mh
next parent reply other threads:[~2002-02-19 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5402-Tue19Feb2002211902+0200-eliz@is.elta.co.il>
2002-02-19 11:31 ` Richard Earnshaw [this message]
2002-02-19 13:06 ` Andrew Cagney
2002-02-19 23:27 ` 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=200202191928.TAA07094@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@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