Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] First cut of SOM and PA64 solib support
Date: Wed, 08 Dec 2004 04:46:00 -0000	[thread overview]
Message-ID: <20041207213322.0f9fcda8.kevinb@redhat.com> (raw)
In-Reply-To: <20041208013849.GF6359@tausq.org>

On Tue, 7 Dec 2004 17:38:49 -0800
Randolph Chung <randolph@tausq.org> wrote:

> One question -- none of the solib* files have entries in fnchange.lst.
> Are any entries needed?

I don't believe so.  Although the filename prefixes (before the ".")
are longer than eight characters, they're all distinguishable from
existing names in the first eight characters.  More concretely,
"solib-so" (from solib-som.[hc]) and "solib-pa" (from
"solib-pa64.[hc]) don't conflict in the first eight characters of any
existing names.  Note that if you ever added a solib-pa32.c, you'd
have to add an entry to fnchange.lst.

(I'm sure that someone who deals with 8.3 systems more than I do will
correct me if I'm wrong...)

Kevin


  reply	other threads:[~2004-12-08  4:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  9:10 [rfc] first cut of solib-som.[ch] Randolph Chung
2004-12-07 17:31 ` Kevin Buettner
2004-12-07 21:41   ` Randolph Chung
2004-12-07 22:18     ` Kevin Buettner
2004-12-07 23:27       ` Randolph Chung
2004-12-08  0:02         ` Kevin Buettner
2004-12-08  1:44           ` [commit] First cut of SOM and PA64 solib support Randolph Chung
2004-12-08  4:46             ` Kevin Buettner [this message]
2004-12-08  5:28             ` Eli Zaretskii
2004-12-08  6:12               ` Randolph Chung
2004-12-08 20:01                 ` 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=20041207213322.0f9fcda8.kevinb@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.org \
    /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