From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Fork event updates, part the eleventh
Date: Mon, 16 Dec 2002 08:44:00 -0000 [thread overview]
Message-ID: <3DFE01FF.7040102@redhat.com> (raw)
In-Reply-To: <20021215201758.GA22617@nevyn.them.org>
> The differences between the FORKED and VFORKED cases were all dead code now,
> so we can bring them together. Committed.
BTW, I think its reasonable to be only committing one of these a day.
Yes it slows you down a little and yes, in theory, no other target can
be broken by this stuff :-/ However, it also means that each change
gets a chance to be tested by others.
enjoy,
Andrew
prev parent reply other threads:[~2002-12-16 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 12:40 Daniel Jacobowitz
2002-12-16 8:44 ` Andrew Cagney [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=3DFE01FF.7040102@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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