From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb@sourceware.org
Cc: mark@codesourcery.com, paul@codesourcery.com, drow@false.org
Subject: Windows support in GDB
Date: Fri, 29 Apr 2005 15:32:00 -0000 [thread overview]
Message-ID: <200504291513.j3TFDhjx021040@elgar.sibelius.xs4all.nl> (raw)
Guys, I'm getting a bit of an uneasy feeling here. It may be that I'm
getting the wrong impression here, but I've seen quite a bit more
Windows-related patches than I had in mind when Mark started submitted
his first patches and said they were fairly limited and mostly some
configure bits. The problem here is that they mostly concern the
non-POSIX nature of Windows, which sets its quit far apart from the
traditional Unix-like systems that have been converging towards POSIX
for quite some time now. This means that we really need to have some
commitment from the Windows user community for maintaining this stuff.
Otherwise this will become another MetroWerks disaster.
It's fairly obvious that this development is coming from CodeSourcery.
There's nothing wrong with that, but I'd like to ask CodeSourcery what
their commitment to maintaining this new code is. In the past we have
seen quite a few contributions from embedded sofware companies. In
many cases these contributions were apparently done as contract work,
and after the work was completed the code was never touched again.
Can CodeSourcery gives some clarification on this matter?
Mark
next reply other threads:[~2005-04-29 15:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 15:32 Mark Kettenis [this message]
2005-04-29 15:32 ` Daniel Jacobowitz
2005-04-29 16:08 ` Christopher Faylor
2005-04-29 16:31 ` Mark Mitchell
2005-04-29 16:36 ` Christopher Faylor
2005-04-29 16:47 ` Mark Mitchell
2005-04-29 16:56 ` Christopher Faylor
2005-04-29 17:05 ` Mark Mitchell
2005-04-29 17:16 ` Christopher Faylor
2005-05-01 20:13 ` Eli Zaretskii
2005-05-01 19:50 ` Eli Zaretskii
2005-04-29 16:52 ` Dave Korn
2005-04-29 16:57 ` Mark Mitchell
2005-04-29 17:00 ` Dave Korn
2005-04-30 16:18 ` Mark Kettenis
2005-04-30 20:37 ` Christopher Faylor
2005-05-01 20:05 ` Eli Zaretskii
2005-05-01 20:06 ` Mark Mitchell
2005-05-01 20:24 ` Eli Zaretskii
2005-04-29 16:32 ` Kris Warkentin
2005-04-29 16:40 ` Christopher Faylor
2005-04-29 17:00 ` Kris Warkentin
2005-05-01 19:55 ` Eli Zaretskii
2005-05-01 21:41 ` Christopher Faylor
2005-05-02 19:03 ` Eli Zaretskii
2005-05-02 19:56 ` Christopher Faylor
2005-04-29 16:48 ` Daniel Jacobowitz
2005-04-29 17:33 ` Christopher Faylor
2005-04-29 17:58 ` Daniel Jacobowitz
2005-04-29 19:08 ` Christopher Faylor
2005-04-29 19:36 ` Daniel Jacobowitz
2005-04-29 22:01 ` Christopher Faylor
2005-05-02 15:41 ` Andrew Cagney
2005-05-02 15:45 ` Daniel Jacobowitz
2005-04-29 16:04 ` Kris Warkentin
2005-04-29 16:23 ` Mark Mitchell
2005-04-29 16:46 ` Christopher Faylor
2005-04-29 16:50 ` Mark Mitchell
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=200504291513.j3TFDhjx021040@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark@codesourcery.com \
--cc=paul@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