From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado via Gdb <gdb@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: Backporting minor fix to older gdb releases
Date: Wed, 15 Mar 2023 17:11:35 +0400 [thread overview]
Message-ID: <ZBHEB1FFcbRpa7+3@adacore.com> (raw)
In-Reply-To: <8d4ac3fc-c508-2a92-5af2-efaa18da7a20@arm.com>
FWIW, there is no real policy that I know of.
We have been known to accept patches on release branches past the .2
release. It's been very rare, though. In all cases, the push was done
with the understanding that there would likely not be another official
release off that branch, so that was purely for the benefit of people
who wanted to build from the HEAD of a release branch rather than from
an official release.
Whether we should be doing it in this case, I don't have a strong
opinion. I think Andrew is making good points, and I'm wondering
whether it will actually serve anyone if we backport the patches.
On the other hand, are the patches extra safe? If they are, perhaps
in the spirit of not standing in the way of someone willing to make
it better for others...
--
Joel
next prev parent reply other threads:[~2023-03-15 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:18 Luis Machado
2023-03-15 11:33 ` Andrew Burgess
2023-03-15 12:26 ` Luis Machado
2023-03-15 13:11 ` Joel Brobecker [this message]
2023-03-15 13:45 ` Luis Machado
2023-03-20 4:18 ` Joel Brobecker
2023-03-22 9:57 ` Luis Machado
2023-04-11 6:04 ` Luis Machado
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=ZBHEB1FFcbRpa7+3@adacore.com \
--to=brobecker@adacore.com \
--cc=aburgess@redhat.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).