From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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:00:00 -0000 [thread overview]
Message-ID: <20050512124142.GA29462@nevyn.them.org> (raw)
In-Reply-To: <01c556d0$Blat.v2.4$7f0d6de0@zahav.net.il>
On Thu, May 12, 2005 at 11:55:30AM +0300, Eli Zaretskii wrote:
> > Date: Fri, 06 May 2005 13:14:08 +0300
> > From: "Eli Zaretskii" <eliz@gnu.org>
> > CC: gdb-patches@sourceware.org
> >
> > > Date: Fri, 6 May 2005 10:07:09 +0200
> > > From: Mark Kettenis <kettenis@gnu.org>
> > > CC: eliz@gnu.org
> > >
> > > Eli, any chance you can get rid of xm-go32.h too?
> >
> > Chance, yes. We have a public holiday coming up, I hope I will have
> > time to finally keep my promise to Andrew.
>
> The holiday came, and here's what I have in my sandbox. Is this way
> of solving the issue of non-standard init file names is acceptable?
> If so, I will commit the changes.
>
> Note that tm-cisco.h and tm-os68k.h override the standard definition
> of GDBINIT_FILENAME. Should we switch those platforms to the dynamic
> initialization as well?
FWIW, I like this solution.
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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-12 12:42 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 [this message]
2005-05-12 13:26 ` Eli Zaretskii
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=20050512124142.GA29462@nevyn.them.org \
--to=drow@false.org \
--cc=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