public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Angela Marie Thomas <angela@foam.wonderslug.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: overseers@sources.redhat.com
Subject: Re: Now I do need PR gdb/701
Date: Thu, 06 Feb 2003 19:37:00 -0000	[thread overview]
Message-ID: <20030206193109.09404D0093@foam.wonderslug.com> (raw)
In-Reply-To: Your message of Thu, 06 Feb 2003 12:48:57 CST. <200302061848.h16ImvK29629@duracef.shout.net>


> I've got this FAIL in gdb HEAD happening in test script gdb.mi/gdb701.exp.
> This is for PR gdb/701, which is missing from the database.
> 
> So not only is it missing, but now it turns out that I actually
> need to read the PR.  Small world.
> 
> Can you recover this, or let me know if it's too much of a hassle
> to recover?
> 
> Here are the messages that I found in gdb-prs archives:
> 
>   http://sources.redhat.com/ml/gdb-prs/2002-q3/msg00238.html
>   http://sources.redhat.com/ml/gdb-prs/2002-q3/msg00240.html
> 
> Michael C

I think someone fixed it.  At least gdb/701 seems to exist now.

There was no gdb/701 in the backups but there was a gdb/701.old.  I'm
guessing that something went wonky with gnats on that day (it was
Fri the 13th after all) which resulted in the failure.

--Angela

  reply	other threads:[~2003-02-06 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 18:48 Michael Elizabeth Chastain
2003-02-06 19:37 ` Angela Marie Thomas [this message]
2003-02-06 19:46   ` Christopher Faylor
2003-02-06 19:54     ` Angela Marie Thomas
2003-02-06 19:57       ` Christopher Faylor
2003-02-06 20:06         ` Angela Marie Thomas
2003-02-06 20:09           ` Jason Molenda
2003-02-06 20:10             ` Christopher Faylor
2003-02-06 20:17               ` Christopher Faylor
2003-02-07  0:05             ` Angela Marie Thomas
2003-02-06 19:49 Michael Elizabeth Chastain
2003-02-07  6:18 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=20030206193109.09404D0093@foam.wonderslug.com \
    --to=angela@foam.wonderslug.com \
    --cc=angela@wonderslug.com \
    --cc=mec@shout.net \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).