Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: ssbssa@yahoo.de, gdb-patches@sourceware.org
Subject: Re: GDB 16.0.90 available for testing
Date: Thu, 02 Jan 2025 19:33:34 +0200	[thread overview]
Message-ID: <868qrtjf2p.fsf@gnu.org> (raw)
In-Reply-To: <Z3Y2u7BZ7MbFgk9X@adacore.com> (message from Joel Brobecker on Thu, 2 Jan 2025 10:48:27 +0400)

> Date: Thu, 2 Jan 2025 10:48:27 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, ssbssa@yahoo.de,
> 	gdb-patches@sourceware.org
> 
> > 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.
> 
> Correct!

Thanks, so I've now cherry-picked that commit to gdb-16-branch.

  reply	other threads:[~2025-01-02 17:34 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
2025-01-02  6:12           ` Eli Zaretskii
2025-01-02  6:48             ` Joel Brobecker
2025-01-02 17:33               ` Eli Zaretskii [this message]
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=868qrtjf2p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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