From: Christopher Faylor <cgf@alum.bu.edu>
To: gdb-patches@sources.redhat.com
Cc: manubee@wanadoo.fr
Subject: Re: Configure GDB for MinGW
Date: Mon, 24 May 2004 21:01:00 -0000 [thread overview]
Message-ID: <20040524210149.GA11067@coe.bosbc.com> (raw)
In-Reply-To: <200405241736.i4OHapkM000351@elgar.kettenis.dyndns.org>
On Mon, May 24, 2004 at 07:36:51PM +0200, Mark Kettenis wrote:
> From: "Manu" <manubee@wanadoo.fr>
> Date: Fri, 21 May 2004 12:04:20 +0200
>
>Thanks for your contribution. I think it is small enough to be
>accepted without a copyright assignment, especially if you follow the
>advice below. I'm not completely sure though.
I guess we'd have to see the actual finished patch but given that it makes
changes to a number of files and adds new functionality, I don't think
it really could be considered trivial.
>A few remarks and questions:
>
>1. Please update the copyright year of new files or files that you changed.
>
>2. Please remove any empty variables in your .mh and .mt files.
>
>3. Is MH_CFLAGS=-D_POSIX in mingw32.mh really necessary?
>
>4. Your nm-mingw32.h file seems to be a verbatim copy if nm-cygwin.h.
> Please use nm-cygwin.h instead.
For consistency with gcc, we could rename this file n-cygming.h.
>5. All your tm-mingw32.h file does in including tm-cygwin.h. Actually
> I think you can just use cygwin.mt instead of mingw32.mt. I expect
> that MinGW uses the same convention for returning structs as
> Cygwin, so that will actually fix a few bugs.
Again, the cygwin.mt file could be renamed.
cgf
next prev parent reply other threads:[~2004-05-24 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 10:05 Manu
2004-05-24 17:36 ` Mark Kettenis
2004-05-24 21:01 ` Christopher Faylor [this message]
2004-05-25 21:32 ` Manu
2004-05-26 2:27 ` Christopher Faylor
2004-05-26 10:41 ` Eli Zaretskii
2004-05-25 21:32 ` Manu
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=20040524210149.GA11067@coe.bosbc.com \
--to=cgf@alum.bu.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=manubee@wanadoo.fr \
/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