From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, ssbssa@yahoo.de, gdb-patches@sourceware.org
Subject: Re: GDB 16.0.90 available for testing
Date: Thu, 2 Jan 2025 05:59:14 +0400 [thread overview]
Message-ID: <Z3Xy8voTZDF17mYF@adacore.com> (raw)
In-Reply-To: <86seq2llua.fsf@gnu.org>
> Alan Modra fixed this bug in Binutils on the master branch, see commit
> b38cf91f230b and https://sourceware.org/bugzilla/show_bug.cgi?id=32507
>
> I'd like to apply the patch to gdb-16-branch, so that GDB 16.1 is
> released without it. Do I cherry-pick the commit from master, or do I
> follow some other procedure? That is, when the release tarball of GDB
> 16.1 is tarred, will it fetch the bfd files from the bfd directory of
> the gdb-16-branch branch?
Correct. Binutils and GDB share the same repository, and when we create
the GDB release branches, we branch everything. So backporting fixes
in bfd follows the same procedure as backporting fixes in the gdb
subdirectory (or any other file of the repositotory).
--
Joel
next prev parent reply other threads:[~2025-01-02 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 3:31 Joel Brobecker
2024-12-29 12:54 ` Eli Zaretskii
2024-12-29 15:11 ` Hannes Domani
2024-12-29 15:33 ` Eli Zaretskii
2025-01-01 13:12 ` Eli Zaretskii
2025-01-02 1:59 ` Joel Brobecker [this message]
2025-01-02 6:12 ` Eli Zaretskii
2025-01-02 6:48 ` Joel Brobecker
2025-01-02 17:33 ` Eli Zaretskii
2025-01-02 17:38 ` Eli Zaretskii
2025-01-03 4:48 ` Joel Brobecker
2025-01-04 10:29 ` Eli Zaretskii
2025-01-02 17:40 ` Eli Zaretskii
2025-01-03 10:05 ` Luis Machado
2025-01-04 10:30 ` Eli Zaretskii
2025-01-04 11:00 ` Tom de Vries
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=Z3Xy8voTZDF17mYF@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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