From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: chromium: update to 88.0.4324.96.
Date: Wed, 27 Jan 2021 13:06:56 +0100 [thread overview]
Message-ID: <20210127120656.aEhqmduEKAjQKG6I5G6P-aiIYnXU3qP9BtBy1ELckbE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28064@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
There's a merged pull request on the void-packages repository
chromium: update to 88.0.4324.96.
https://github.com/void-linux/void-packages/pull/28064
Description:
[ci skip]
- Built for x86_64, x86_64-musl, i686.
- Tested on x86_64.
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
@q66 I had to make some changes to one **ppc64** patch to change some `#define`s... please verify that I did this properly.
prev parent reply other threads:[~2021-01-27 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 22:33 [PR PATCH] " pbui
2021-01-21 18:20 ` [PR PATCH] [Updated] " pbui
2021-01-24 21:07 ` ericonr
2021-01-26 14:58 ` ericonr
2021-01-26 14:58 ` ericonr
2021-01-26 15:37 ` [PR PATCH] [Updated] " pbui
2021-01-26 15:39 ` pbui
2021-01-27 12:06 ` q66 [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=20210127120656.aEhqmduEKAjQKG6I5G6P-aiIYnXU3qP9BtBy1ELckbE@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).