From: Mark Kettenis <kettenis@gnu.org>
To: randolph@tausq.org
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Fix "info shared" on 32-bit (SOM) HP-UX
Date: Sun, 05 Dec 2004 20:04:00 -0000 [thread overview]
Message-ID: <200412051946.iB5Jke2k001693@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20041205193717.GW6359@tausq.org> (message from Randolph Chung on Sun, 5 Dec 2004 11:37:17 -0800)
Date: Sun, 5 Dec 2004 11:37:17 -0800
From: Randolph Chung <randolph@tausq.org>
> This should all be temporary; we should make an effort *soon* to get
> somsolib.c integrated in the solib.c framework of handling shared
> libraries. But at least this allows us to get a reasonable baseline.
>
> OK?
yes, ok with me. i started working on solib-som.[ch] but got
sidetracked.... will try to get back to it soon.
Great! Thanks! I committed the patch.
Mark
prev parent reply other threads:[~2004-12-05 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 18:46 Mark Kettenis
2004-12-05 19:49 ` Randolph Chung
2004-12-05 20:04 ` Mark Kettenis [this message]
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=200412051946.iB5Jke2k001693@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=brobecker@adacore.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