Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb-7.11.1 re-spin update
Date: Mon, 02 May 2016 21:30:00 -0000	[thread overview]
Message-ID: <46a26fd1-265a-4140-0a39-16b93d59a628@redhat.com> (raw)
In-Reply-To: <20160502211620.GC4771@adacore.com>

On 05/02/2016 10:16 PM, Joel Brobecker wrote:
>>> It looks like https://sourceware.org/bugzilla/show_bug.cgi?id=20029
>>> had its target milestone set to 7.11.1 by the reporter (nightstrike).
>>
>> That was actually me.  You can tell from:
>>
>> Pedro Alves <palves at redhat dot com> changed:
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> (...)
>>    Target Milestone|---                         |7.11.1
> 
> Is that from the email sent to gdb-prs?

Yes, from:

 https://sourceware.org/ml/gdb-prs/2016-q2/msg00171.html

(Actually, the "From:" field also mentions my account.)

> I was looking for this info
> in the PR's log, and couldn't find that information. 

Yeah.  I don't know how to get that info out of bugzilla directly.

> Not a problem,
> > though, since the wiki wouldn't be doing any better in this area...

Yeah, it's at least archived in the gdb-prs mailing list archive.

Thanks,
Pedro Alves


  reply	other threads:[~2016-05-02 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 21:50 Joel Brobecker
2016-04-26 12:16 ` Pedro Alves
2016-05-02 15:46   ` Joel Brobecker
2016-05-02 17:23     ` Pedro Alves
2016-05-02 19:38       ` Joel Brobecker
2016-05-02 19:41         ` Pedro Alves
2016-05-02 21:16           ` Joel Brobecker
2016-05-02 21:30             ` Pedro Alves [this message]
2016-05-05 13:49               ` Joel Brobecker
2016-04-27 19:36 ` Jan Kratochvil
2016-05-03 14:19 ` Simon Marchi
2016-05-03 14:31   ` Joseph Myers
2016-05-03 15:01     ` Simon Marchi

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=46a26fd1-265a-4140-0a39-16b93d59a628@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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