From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: 2 weeks to GDB 7.10 tentative branching date!
Date: Wed, 03 Jun 2015 17:32:00 -0000 [thread overview]
Message-ID: <20150603173242.GC2801@adacore.com> (raw)
In-Reply-To: <20150603171341.GA13342@host1.jankratochvil.net>
> On Wed, 03 Jun 2015 19:06:10 +0200, Joel Brobecker wrote:
> > Same here, but I think there is a chance that we can backport
> > the fixes to the branch prior to making the release, as they should
> > only affect the "compile" feature?
>
> Yes.
I've "opened" the sections that deal with updates after branch
creation. Can you add the first item in the "before branch creation"
section, and the rest if the "GDB 7.10 Release" section? You can use
the GDB 7.9 release page as a guideline for the format:
https://sourceware.org/gdb/wiki/GDB_7.9_Release
Thanks!
--
Joel
next prev parent reply other threads:[~2015-06-03 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 21:37 Joel Brobecker
2015-06-02 8:12 ` Jan Kratochvil
2015-06-02 8:16 ` Phil Muldoon
2015-06-03 17:06 ` Joel Brobecker
2015-06-03 17:13 ` Jan Kratochvil
2015-06-03 17:32 ` Joel Brobecker [this message]
2015-06-03 19:01 ` GDB Bugzilla Target Milestone 7.10 [Re: 2 weeks to GDB 7.10 tentative branching date!] Jan Kratochvil
2015-06-02 16:21 ` 2 weeks to GDB 7.10 tentative branching date! Yao Qi
2015-06-02 16:33 ` Jan Kratochvil
2015-06-02 20:45 ` Philippe Waroquiers
2015-06-03 17:38 ` Joel Brobecker
2015-06-03 20:06 ` Philippe Waroquiers
2015-06-03 18:08 ` Doug Evans
2015-06-04 17:25 ` Doug Evans
2015-06-15 13:58 ` GDB 7.10 new branching date: Jun 29th, 2015 (was: "Re: 2 weeks to GDB 7.10 tentative branching date!") Joel Brobecker
2015-07-02 15:53 ` GDB 7.10 new branching date: Jun 29th, 2015 Yao Qi
2015-07-02 17:18 ` Joel Brobecker
2015-07-03 10:23 ` Gary Benson
2015-07-06 11:11 ` Yao Qi
2015-07-06 16:37 ` Joel Brobecker
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=20150603173242.GC2801@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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).