From: Joel Brobecker <brobecker@adacore.com>
To: Japin Li via Gdb <gdb@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: Question about gdb bugfix backpatch policy
Date: Tue, 24 May 2022 19:02:45 -0700 [thread overview]
Message-ID: <Yo2ORaw9a1ALvOET@adacore.com> (raw)
In-Reply-To: <MEYP282MB1669ED0E3BF7CEC0B32AC961B6D69@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM>
Hello,
> Recently, I have a segfault using GDB 8.1.1. After search, I found it
> [1] fixed in later version (such as GDB 12.1). I want to know why
> this doestn't backpatch to where it occurs?
>
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=23613
In the GDB project, we only maintain 1 active release branch
(in addition to our main development branch). When we make fixes,
we normally make the fix on the main development branch first,
and then a selection of those patches, based on how important
and safe they are, are also backported to the one active release
branch.
In this case, the GDB 8.1 release branch was closed by the time
this fix was pushed. It was therefore to late to even consider
including it in 8.1.1.
--
Joel
prev parent reply other threads:[~2022-05-25 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 1:41 Japin Li
2022-05-25 2:02 ` Joel Brobecker [this message]
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=Yo2ORaw9a1ALvOET@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).