Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: mark@codesourcery.com, drow@false.org, paul@codesourcery.com,
	gdb@sourceware.org, Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: Windows support in GDB
Date: Sat, 30 Apr 2005 20:37:00 -0000	[thread overview]
Message-ID: <20050430161758.GB2396@trixie.casa.cgf.cx> (raw)
In-Reply-To: <200504301429.j3UETn7w020204@elgar.sibelius.xs4all.nl>

On Sat, Apr 30, 2005 at 04:29:49PM +0200, Mark Kettenis wrote:
>   Date: Fri, 29 Apr 2005 09:56:08 -0700
>   From: Mark Mitchell <mark@codesourcery.com>
>
>"Oh my god.  What did I do!"
>
>Anyway, I want to thank Mark and Daniel for explaining a bit of the
>background.  The key point is that there will be people tracking gdb
>on MinGW systems fixing any accidental breakage, and willing to answer
>questions about MinGW-specific questions.  That seems to be the case.
>It'd be great if this could somehow be formalized by having a MinGW
>host maintainer (then we could clarify Christophers role as Cygwin
>host & native).

I am willing to continue to be the Windows maintainer.  Most of the
issues that I deal with in gdb are Windows related, not cygwin related.
It wouldn't make sense to have someone else worrying about Windows.

cgf


  reply	other threads:[~2005-04-30 16:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 15:32 Mark Kettenis
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 [this message]
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=20050430161758.GB2396@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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