From: Nick Clifton <nickc@redhat.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>,
binutils@sourceware.org
Subject: Re: Open branches for backports
Date: Tue, 10 Jan 2023 12:29:05 +0000 [thread overview]
Message-ID: <a0f00d13-e72e-cd8d-df9f-65b3393e332d@redhat.com> (raw)
In-Reply-To: <Y71T54u8LgAwE0lU@li-42a4824c-28a0-11b2-a85c-f55c0d5956ce.ibm.com>
Hi Stefan,
> I'm preparing a target specific fix which I would like to backport.
> Which branches are currently open for backports?
Generally speaking we only accept backports to the most recent release
branch. So in this case that would mean the 2.39 branch. But ...
... The 2.40 branch has been created and is currently accepting bug
fix backports. So if your fix is submitted soon, it may get in before
the release actually happens. Once the 2.40 release is out of the door,
the 2.40 branch will then be the branch suitable for receiving backports.
It is possible to apply patches to other, earlier branches as well. But
it is very unlikely that there will ever be any more official releases
made from those old branches.
> Just for the future,
> is there a place where this information is kept
There is a small reference to this issue in the binutils/MAINTAINERS file
where it says:
"If a patch is approved for check in to the mainline
sources, it can also be checked into the current
release branch."
But it could be publicised more widely. I feel like this is something
that should be mentioned on the Binutils wiki as well.
> or should I just ask on the mailinglist again?
You can always do that too.
Cheers
Nick
next prev parent reply other threads:[~2023-01-10 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 12:02 Stefan Schulze Frielinghaus
2023-01-10 12:29 ` Nick Clifton [this message]
2023-01-10 13:33 ` Stefan Schulze Frielinghaus
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=a0f00d13-e72e-cd8d-df9f-65b3393e332d@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=stefansf@linux.ibm.com \
/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).