From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org
Subject: Re: Buildbot improvements
Date: Wed, 14 Jul 2021 17:10:25 -0400 [thread overview]
Message-ID: <xn35sgr48u.fsf@greed.delorie.com> (raw)
In-Reply-To: <5afdcee8-d5c5-9e7a-c7a5-4a9546393021@redhat.com>
"Carlos O'Donell" <carlos@redhat.com> writes:
> ... however, we could output a set of instructions that when used in
> a script could reconstitute the built container?
That's the "I can't guarantee the same contents as was built" case since
the underlying Fedora container might have changed.
But otherwise, yes. You'd have to insert the right glibc git tree and
patch, but the container descriptions are tiny.
next prev parent reply other threads:[~2021-07-14 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 18:18 Adhemerval Zanella
2021-07-13 19:15 ` DJ Delorie
2021-07-14 20:43 ` Carlos O'Donell
2021-07-14 21:10 ` DJ Delorie [this message]
2021-07-14 21:58 ` Adhemerval Zanella
2021-07-15 4:11 ` DJ Delorie
2021-07-15 12:24 ` Carlos O'Donell
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=xn35sgr48u.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--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).