Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: gdb-18 branch FROZEN
Date: Thu, 06 Aug 2026 18:24:41 +0100	[thread overview]
Message-ID: <6a74c35a.89544747.3fcae.4eb4@mx.google.com> (raw)


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 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,
-- 
Andrew Burgess


             reply	other threads:[~2026-08-06 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 17:24 Andrew Burgess [this message]
2026-08-06 18:11 ` gdb-18 branch now *OPEN* (was: "gdb-18 branch FROZEN") 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=6a74c35a.89544747.3fcae.4eb4@mx.google.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