public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: overseers@sourceware.org
Cc: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
	 Joel Brobecker <brobecker@adacore.com>
Subject: Fwd: [Bug core/11166] GDB complains of not finding files.
Date: Mon, 16 May 2016 16:27:00 -0000	[thread overview]
Message-ID: <CADPb22TvRomz+R_jDM9_9VsgS-V6c4GON_UWFw3P5jNbr-D3jg@mail.gmail.com> (raw)
In-Reply-To: <bug-11166-4717-fQ7tNZL1VJ@http.sourceware.org/bugzilla/>

Hi.
There are a bunch of these kinds of changes. I can't imagine them being legit.
Is there a way to kick this guy out of bugzilla?
[And the sooner the better, before more damage is done.]



---------- Forwarded message ----------
From: gobisha6355 at gmail dot com <sourceware-bugzilla@sourceware.org>
Date: Mon, May 16, 2016 at 8:18 AM
Subject: [Bug core/11166] GDB complains of not finding files.
To: gdb-prs@sourceware.org


https://sourceware.org/bugzilla/show_bug.cgi?id=11166

shanjay <gobisha6355 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P2
             Status|UNCONFIRMED                 |NEW
            Version|7.0                         |unspecified
   Last reconfirmed|                            |2016-05-16
          Component|gdb                         |core
     Ever confirmed|0                           |1
   Target Milestone|7.1                         |---
            Product|gdb                         |netresolve

--
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2016-05-16 16:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-11166-4717-fQ7tNZL1VJ@http.sourceware.org/bugzilla/>]

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=CADPb22TvRomz+R_jDM9_9VsgS-V6c4GON_UWFw3P5jNbr-D3jg@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=overseers@sourceware.org \
    --cc=palves@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).