From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Peter Bergner <bergner@linux.ibm.com>,
GNU C Library <libc-alpha@sourceware.org>
Cc: Manjunath Matti <mmatti@linux.ibm.com>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Question on backporting. [Was Re: [PATCH v2 2/2] powerpc: Add HWCAP3/HWCAP4 data to TCB for Power Architecture.]
Date: Wed, 20 Mar 2024 17:09:12 -0300 [thread overview]
Message-ID: <dbaa3359-56f6-455f-aadd-281f47942028@linaro.org> (raw)
In-Reply-To: <87o7b8hgap.fsf@ascii.art.br>
On 20/03/24 16:08, Tulio Magno Quites Machado Filho wrote:
> Peter Bergner <bergner@linux.ibm.com> writes:
>
>> As someone new to the Power maintainership role, can someone help explain
>> the process/rules for backporting changes into the release branches?
>
> I like the explanation from this section of the wiki:
> https://sourceware.org/glibc/wiki/Release/#General_policy
>
>> As port maintainer do I have discretion to decide whether this patch
>> can be backported to the release branches or do I need consensus that
>> backporting it is ok?
>
> In my interpretation, consensus is still important, but your input is
> also very important.
> With that said I believe both patches fall into the following:
>
> ... any patch on master that doesn't change ABI or API is immediately
> suitable for backporting to a stable branch.
>
> This is what I'd do, assuming there are no time constraints:
>
> 1. Submit both patches to libc-stable.
> 2. If nobody objects, push the changes to the stable branch.
>
Both patch should be ok to backport, since the trickiest that added
__tcb_parse_hwcap_and_convert_at_platform was done on 2.39.
prev parent reply other threads:[~2024-03-20 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 14:50 Peter Bergner
2024-03-20 19:08 ` Tulio Magno Quites Machado Filho
2024-03-20 20:09 ` Adhemerval Zanella Netto [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=dbaa3359-56f6-455f-aadd-281f47942028@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bergner@linux.ibm.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mmatti@linux.ibm.com \
--cc=tuliom@ascii.art.br \
/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).