Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix test script ERRORs in 5.1 branch
Date: Sun, 13 Jan 2002 20:17:00 -0000	[thread overview]
Message-ID: <200201140417.WAA18844@duracef.shout.net> (raw)

> Michael, pulling the test cases over doesn't worry me.  Er, almost.  The 
> trunk contains some recently OBSOLETE code so you'd need care there.

Cool.

I plan to keep testing and reporting on gdb_5_1-2001-07-29-branch
for a little while longer, just in case another release might come
from it.

The real work is proportional to:

  delta # of changes in test results
  absolute # of ERRORs and WARNINGs

Michael C
(working on my weekend report right now)


             reply	other threads:[~2002-01-14  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 20:17 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-13 19:47 Michael Elizabeth Chastain
2002-01-13 19:53 ` Daniel Jacobowitz
2002-01-13 20:10   ` Andrew Cagney

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=200201140417.WAA18844@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@cygnus.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