From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, kettenis@chello.nl
Subject: Re: [PATCH] Testsuite: deal gracefully with lack of pthreads
Date: Sat, 01 Feb 2003 17:47:00 -0000 [thread overview]
Message-ID: <200302011747.h11HlhF21271@duracef.shout.net> (raw)
Mark K asks:
> 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?
This issue has come up before.
Since there haven't been any entries to gdb.mi/ChangeLog in 2003,
I propose a bit of a kludge:
split testsuite/gdb.mi/ChangeLog to gdb.mi/ChangeLog.{1999,2000,2001,2002}
cvs remove testsuite/gdb.mi/ChangeLog
use testsuite/ChangeLog now and in the future
My two cents,
Michael C
next reply other threads:[~2003-02-01 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 17:47 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-01 16:24 Mark Kettenis
2003-02-01 16:40 ` Andrew Cagney
2003-02-01 22:37 ` Mark Kettenis
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=200302011747.h11HlhF21271@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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