From: Doug Evans <dje@google.com>
To: overseers@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Fwd: GDB Bugzilla Target Milestone 7.10 [Re: 2 weeks to GDB 7.10 tentative branching date!]
Date: Mon, 08 Jun 2015 06:32:00 -0000 [thread overview]
Message-ID: <CADPb22ROJLVZcLu3dhcSGEWBm=N=4fT8HfhNmQvuQKt9wz0+Eg@mail.gmail.com> (raw)
In-Reply-To: <20150603190146.GA15887@host1.jankratochvil.net>
Hi. Can you add "7.10" as a "Target Milestone" for gdb bugzilla?
TIA
---------- Forwarded message ----------
From: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Wed, Jun 3, 2015 at 12:01 PM
Subject: GDB Bugzilla Target Milestone 7.10 [Re: 2 weeks to GDB 7.10
tentative branching date!]
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
On Wed, 03 Jun 2015 19:32:42 +0200, Joel Brobecker wrote:
> Can you add the first item in the "before branch creation" section,
GDB Bugzilla does not have "Target Milestone" = "7.10".
Jan
parent reply other threads:[~2015-06-08 6:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150603190146.GA15887@host1.jankratochvil.net>]
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='CADPb22ROJLVZcLu3dhcSGEWBm=N=4fT8HfhNmQvuQKt9wz0+Eg@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=jan.kratochvil@redhat.com \
--cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).