Re: GDB 16.0.90 available for testing

[Eli Zaretskii <eliz@gnu.org>]

> Date: Thu, 2 Jan 2025 05:59:14 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: brobecker@adacore.com, ssbssa@yahoo.de, gdb-patches@sourceware.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).

OK, thanks.  Just to be sure I understand: the repository is shared,
but branches are separate, right?  So when I cherry-pick a commit to
gdb-16-branch, I don't affect any branches that Binutils will use for
their releases, right?  Otherwise, cherry-picking would need to be
coordinated with the Binutils folks.