public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
	 Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	Szabolcs Nagy <Szabolcs.Nagy@arm.com>,
	 Stefan Liebler <stli@linux.ibm.com>,
	 "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	DJ Delorie <dj@redhat.com>, nd <nd@arm.com>
Subject: Re: [PATCH] test-container: Install with $(sorted-subdirs) [BZ #24794]
Date: Thu, 27 Jan 2022 07:25:30 -0800	[thread overview]
Message-ID: <CAMe9rOpCFbpCCNeQFNQP8mz=u-qm1X6wt+ar1YPLkmOpJpUKyg@mail.gmail.com> (raw)
In-Reply-To: <87h875ynbj.fsf@linux.ibm.com>

On Mon, Jul 29, 2019 at 6:37 AM Tulio Magno Quites Machado Filho
<tuliom@linux.ibm.com> wrote:
>
> Carlos O'Donell <carlos@redhat.com> writes:
>
> > On 7/25/19 8:46 AM, Szabolcs Nagy wrote:
> >> On 25/07/2019 01:03, Tulio Magno Quites Machado Filho wrote:
> >>> Commit 35e038c1d2ccb3a75395662f9c4f28d85a61444f started to use an
> >>> incomplete list of subdirs based on $(all-subdirs) causing
> >>> testroot.pristine to miss files from nss.
> >>>
> >>> Tested if the list of files in testroot.pristine remains the same.
> >>
> >> fwiw with this patch aarch64 buildbot would go back to green.
> >
> > This is good enough confirmation for me.
> >
> > Please install the fix so we can get clean builds for the release.
>
> I've just pushed it to master.
>
> DJ,
> I took the freedom to add your name to the ChangeLog file too as you proposed
> the same fix.  ;-)
>
> Pushed as 354e4c1adddb1.
>
> --
> Tulio Magno

I am backporting this to older release branches.

-- 
H.J.

           reply	other threads:[~2022-01-27 15:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87h875ynbj.fsf@linux.ibm.com>]

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='CAMe9rOpCFbpCCNeQFNQP8mz=u-qm1X6wt+ar1YPLkmOpJpUKyg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@sourceware.org \
    --cc=nd@arm.com \
    --cc=stli@linux.ibm.com \
    --cc=tuliom@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).