From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Testsuite: deal gracefully with lack of pthreads
Date: Sat, 01 Feb 2003 22:37:00 -0000 [thread overview]
Message-ID: <200302012237.h11MbnPl023855@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3E3BF876.3040506@redhat.com> (message from Andrew Cagney on Sat, 01 Feb 2003 11:40:22 -0500)
Date: Sat, 01 Feb 2003 11:40:22 -0500
From: Andrew Cagney <ac131313@redhat.com>
> This patch parallels what Daniel has done to the tests in the
> gdb.threads subdir.
>
> Elana, Andrew, OK to check this in?
yes.
Done.
> There's probably one issue: We have a ChangeLog in both testsuite and
> testsuite/gdb.mi. Both seem to be in used for MI tests. Which one is
> preferred, and can we think of a way to avoid that both are used?
I don't know.... Probably (I'm not sure I should be saying this) merge
gdb.mi/ChangeLog into ChangeLog.
OK, I added the ChangeLog entries to testsuite/ChangeLog.
Mark
next prev parent reply other threads:[~2003-02-01 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 16:24 Mark Kettenis
2003-02-01 16:40 ` Andrew Cagney
2003-02-01 22:37 ` Mark Kettenis [this message]
2003-02-01 17:47 Michael Elizabeth Chastain
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=200302012237.h11MbnPl023855@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.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