From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix prototype related breakage in go32-nat.c
Date: Sat, 11 Apr 2009 21:41:00 -0000 [thread overview]
Message-ID: <83prfiool0.fsf@gnu.org> (raw)
In-Reply-To: <200904112102.57302.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 11 Apr 2009 21:02:57 +0100
>
> <http://sourceware.org/gdb/wiki/BuildingOnDJGPP>
Thanks for posting that page, I forgot about it.
As it happens, I already found the reasons for all the problems you
describe there (and for a few more), and will be posting patches for
them some time next week.
Once the problems are solved in CVS, is there something we should do
with the above page?
prev parent reply other threads:[~2009-04-11 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 18:00 Eli Zaretskii
2009-04-11 18:15 ` Pedro Alves
2009-04-11 19:27 ` Eli Zaretskii
2009-04-11 20:02 ` Pedro Alves
2009-04-11 21:26 ` Eli Zaretskii
2009-04-13 16:51 ` Tom Tromey
2009-04-13 18:38 ` Eli Zaretskii
2009-04-11 21:41 ` Eli Zaretskii [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=83prfiool0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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