From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: gdb-18 branch FROZEN
Date: Fri, 25 Sep 2026 15:26:00 +0100 [thread overview]
Message-ID: <87se2x1k7b.fsf@redhat.com> (raw)
In-Reply-To: <6ab67218.426fc1f0.188791.ba9b@mx.google.com>
Hi everyone,
I have the release tarballs, so the gdb-18-branch is now unfrozen.
Cheers,
Andrew
Andrew Burgess <aburgess@redhat.com> writes:
> Hello everyone,
>
> Please avoid pushing any commit to the gdb-18-branch branch during
> the next few hours. I am working on creating the next 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,
> --
> Andrew Burgess
next prev parent reply other threads:[~2026-09-25 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:07 Andrew Burgess
2026-09-25 14:26 ` Andrew Burgess [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-06 17:24 Andrew Burgess
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=87se2x1k7b.fsf@redhat.com \
--to=aburgess@redhat.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