Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Mitchell <mark@codesourcery.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Guard uses of fork
Date: Wed, 16 Mar 2005 19:58:00 -0000	[thread overview]
Message-ID: <01c52a61$Blat.v2.4$ef1740c0@zahav.net.il> (raw)
In-Reply-To: <423860D8.2050605@codesourcery.com> (message from Mark Mitchell on Wed, 16 Mar 2005 08:37:44 -0800)

> Date: Wed, 16 Mar 2005 08:37:44 -0800
> From: Mark Mitchell <mark@codesourcery.com>
> CC: gdb-patches@sources.redhat.com
> 
> Daniel Jacobowitz wrote:
> 
> > This is OK.  I'm not sure my understanding of the DJGPP bits is
> > correct, but this patch is safe whether I was right or wrong, which is
> > why I like it.
> 
> Applied, thanks!

In the future, when a patch touches something that is related to the
DJGPP port, I'd appreciate if people would wait with committing the
changes until I had the chance to review and okay it.  Even if the
patch looks obviously correct, like in this case.  That's because the
way the DJGPP port is configured and built is tricky and some of its
subtle aspects are just that--subtle.

(And if I don't respond within a day, ping me: I sometimes miss the
original message due to lack of time to read every line.)

TIA


  reply	other threads:[~2005-03-16 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  4:00 Mark Mitchell
2005-03-16 15:29 ` Daniel Jacobowitz
2005-03-16 16:37   ` Mark Mitchell
2005-03-16 19:58     ` Eli Zaretskii [this message]
2005-03-16 19:50   ` Eli Zaretskii
2005-03-16 19:51     ` Daniel Jacobowitz

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='01c52a61$Blat.v2.4$ef1740c0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark@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