From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>, libc-alpha@sourceware.org
Subject: Re: RFC: Backport architecture specific improvements to release branches
Date: Tue, 29 Mar 2022 16:36:16 -0300 [thread overview]
Message-ID: <50148656-3a64-bb8b-c76c-81451093c65a@linaro.org> (raw)
In-Reply-To: <10492228.4vTCxPXJkl@pinacolada>
On 29/03/2022 16:33, Andreas K. Huettel via Libc-alpha wrote:
> Hi,
>
>> We'd like to backport architecture specific improvements to release branches,
>> similar to backports under sysdeps/x86_64/multiarch on users/intel/x86/2.34
>> branch:
>
> please, if you do this, when possible make some well-defined patch series
> (with a start and end) instead of a continuous trickle of fixes and improvements.
>
> [When I tried to make a cutoff for the 2.34 patchlevel to be "stabilized" for Gentoo,
> I was never sure if the series is finished or if another important thing follows
> in a few days...]
>
> Thanks a lot for your work.
>
> Cheers,
> Andreas
>
Specially for release branches, each patch should be self-contained (meaning it builds
and do not trigger any regression). Are you seeing something differently?
next prev parent reply other threads:[~2022-03-29 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:28 H.J. Lu
2022-03-29 17:36 ` Noah Goldstein
2022-03-29 19:02 ` H.J. Lu
2022-03-29 19:19 ` Noah Goldstein
2022-03-29 19:29 ` Adhemerval Zanella
2022-03-29 21:21 ` H.J. Lu
2022-03-29 19:32 ` Adhemerval Zanella
2022-03-29 19:33 ` Andreas K. Huettel
2022-03-29 19:36 ` Adhemerval Zanella [this message]
2022-03-29 19:40 ` Andreas K. Huettel
2022-04-12 11:49 ` Florian Weimer
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=50148656-3a64-bb8b-c76c-81451093c65a@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@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).