From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com, dave.korn@artimi.com,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH] Your patch from 20050512 b0rked on cygwin!
Date: Sun, 18 Sep 2005 01:34:00 -0000 [thread overview]
Message-ID: <20050918013326.GS8777@nevyn.them.org> (raw)
In-Reply-To: <20050918013107.GA16204@trixie.casa.cgf.cx>
On Sat, Sep 17, 2005 at 09:31:07PM -0400, Christopher Faylor wrote:
> On Sat, Sep 17, 2005 at 09:23:30PM -0400, Daniel Jacobowitz wrote:
> >Dave, is Cygwin really still broken? I never saw a followup to this.
>
> Uh. Huh?
>
> http://sources.redhat.com/ml/gdb-patches/2005-09/msg00088.html
Oh, sorry. This is why patch pings should be threaded with the others;
it sorted out somewhere else in my mailbox.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-09-18 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 17:59 Dave Korn
2005-08-17 19:25 ` Mark Kettenis
2005-09-18 1:23 ` Daniel Jacobowitz
2005-09-18 1:31 ` Christopher Faylor
2005-09-18 1:34 ` Daniel Jacobowitz [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=20050918013326.GS8777@nevyn.them.org \
--to=drow@false.org \
--cc=dave.korn@artimi.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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