From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Get rid of xm-go32.h (was: [COMMIT] Get rid of xm-cygwin.h)
Date: Thu, 12 May 2005 13:26:00 -0000 [thread overview]
Message-ID: <01c556f5$Blat.v2.4$15676100@zahav.net.il> (raw)
In-Reply-To: <20050512124142.GA29462@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 12 May 2005 08:41:42 -0400)
> Date: Thu, 12 May 2005 08:41:42 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
>
> FWIW, I like this solution.
Thanks for reviewing the patch.
> Do we still need either of those targets? I haven't seen reports of
> anyone using them in the time I've been a GDB developer.
If we think they are no longer needed, we should begin by declaring
them obsolete in NEWS. We could then stop bothering about updating
them.
next prev parent reply other threads:[~2005-05-12 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 8:07 [COMMIT] Get rid of xm-cygwin.h Mark Kettenis
2005-05-06 10:16 ` Eli Zaretskii
2005-05-12 12:16 ` [RFA] Get rid of xm-go32.h (was: [COMMIT] Get rid of xm-cygwin.h) Eli Zaretskii
2005-05-12 13:00 ` Daniel Jacobowitz
2005-05-12 13:26 ` Eli Zaretskii [this message]
2005-05-12 19:08 ` Mark Kettenis
2005-05-12 21:46 ` 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='01c556f5$Blat.v2.4$15676100@zahav.net.il' \
--to=eliz@gnu.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