From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [0/8] solib handler rework
Date: Wed, 24 Oct 2007 19:29:00 -0000 [thread overview]
Message-ID: <uodeotixg.fsf@gnu.org> (raw)
In-Reply-To: <20071024114822.GB18617@caradoc.them.org> (message from Daniel Jacobowitz on Wed, 24 Oct 2007 07:48:22 -0400)
> Date: Wed, 24 Oct 2007 07:48:22 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> > The pa64-hpux debugger is pretty broken, so we can't verify them any
> > further. We should probably document that fact somewhere, maybe in
> > the NEWS file?
>
> Poor outdated PROBLEMS, I suppose.
I think we should reserve PROBLEMS for issues for which we can offer a
solution or a workaround. If we want to say that a port is broken,
that should go into NEWS, like we do with deprecated and deleted
targets.
next prev parent reply other threads:[~2007-10-24 19:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 21:32 Ulrich Weigand
2007-10-22 3:31 ` Joel Brobecker
2007-10-22 4:17 ` Joel Brobecker
2007-10-22 18:47 ` Joel Brobecker
2007-10-22 20:42 ` Ulrich Weigand
2007-10-24 6:38 ` Joel Brobecker
2007-10-24 7:59 ` Joel Brobecker
2007-10-24 11:48 ` Daniel Jacobowitz
2007-10-24 19:29 ` Eli Zaretskii [this message]
2007-10-24 19:21 ` Eli Zaretskii
2007-10-24 19:23 ` Joel Brobecker
2007-10-22 13:44 ` Ulrich Weigand
2007-10-22 17:51 ` Joel Brobecker
2007-10-22 20:03 ` Ulrich Weigand
2007-10-24 6:05 ` Joel Brobecker
2007-10-24 21:25 ` Ulrich Weigand
2007-10-22 10:00 ` Pedro Alves
2007-10-23 10:16 ` Pedro Alves
2007-10-23 13:12 ` Ulrich Weigand
2007-10-24 13:03 ` Daniel Jacobowitz
2007-10-24 15:46 ` Kevin Buettner
2007-10-24 22:02 ` Ulrich Weigand
2007-10-25 8:12 ` Mark Kettenis
2007-10-29 20:06 ` i386-nto support (was: Re: [0/8] solib handler rework) Ulrich Weigand
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=uodeotixg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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