From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: gdb-10-branch now OPEN again (was: "gdb-10 branch FROZEN")
Date: Sat, 24 Oct 2020 08:46:53 +0400 [thread overview]
Message-ID: <20201024044653.GA1003313@adacore.com> (raw)
In-Reply-To: <20201024042212.A6A03A0345@float.home>
Hi everyone,
I have the release tarballs, so the gdb-10-branch is now open again
for patches.
As a small reminder, now that the first official release has been
created, future patches going into the gdb-10-branch need to have
a corresponding PR number. The PR number is used as an anchor to
the correspoding info in bugzilla, so people can quickly get more
information about what fixes were made in the .2.
Thank you!
--
Joel
prev parent reply other threads:[~2020-10-24 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 4:22 gdb-10 branch FROZEN Joel Brobecker
2020-10-24 4:46 ` Joel Brobecker [this message]
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=20201024044653.GA1003313@adacore.com \
--to=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