From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Run follow-fork tests on Linux
Date: Mon, 28 Nov 2005 14:00:00 -0000 [thread overview]
Message-ID: <4387DE7A.4070504@redhat.com> (raw)
In-Reply-To: <20051125233347.GA10519@nevyn.them.org>
Daniel Jacobowitz wrote:
> ... you are testing this on something close to HEAD, right? That
> shouldn't be printed unless "set debug linux-nat 1".
Right. In view of Mark's comment, which I assume you second,
that chunk can go. But it could as well stay, too, since it's
harmless and makes the test strings more consistant with one
another.
I can go either way.
prev parent reply other threads:[~2005-11-26 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 0:05 Michael Snyder
2005-11-26 3:58 ` Andreas Schwab
2005-11-28 8:26 ` Michael Snyder
2005-11-26 4:01 ` Mark Kettenis
2005-11-28 13:01 ` Michael Snyder
2005-11-26 4:03 ` Daniel Jacobowitz
2005-11-28 14:00 ` Michael Snyder [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=4387DE7A.4070504@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@false.org \
--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