From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: gdb-13 branch FROZEN
Date: Thu, 2 Feb 2023 07:47:35 +0400 (+04) [thread overview]
Message-ID: <20230202034735.E86A2814D8@takamaka.gnat.com> (raw)
Hello everyone,
Please avoid pushing any commit to the gdb-13-branch branch during
the next few hours. I am working on creating the next pre-release
off this branch.
Also, if at all possible, it saves me a bit of time if you can avoid
pushing changes to the master branch, as it would force me
to handle rebasing and possibly conflict resolution.
I will send a followup message when the branch is open again.
Thank you,
--
Joel Brobecker
next reply other threads:[~2023-02-02 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 3:47 Joel Brobecker [this message]
2023-02-02 5:26 ` gdb-13-branch OPEN again (was: "gdb-13 branch FROZEN") Joel Brobecker
2023-02-19 13:42 gdb-13 branch FROZEN Joel Brobecker
2023-05-27 9:41 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=20230202034735.E86A2814D8@takamaka.gnat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).