From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gperftools: refresh patches
Date: Sun, 03 Jul 2022 23:23:19 +0200 [thread overview]
Message-ID: <20220703212319.AWVeTHVf227aW_zt6SNZzdsBOEUSO_0yAhoVpYX3O0c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37816@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
There's a merged pull request on the void-packages repository
gperftools: refresh patches
https://github.com/void-linux/void-packages/pull/37816
Description:
Package no longer builds with the patch whitespace changes.
The patches which had any looseness have been regenerated
to ensure clean build.
Let me note that there are new recent versions. As I can't
test most of those releases on the rest of Void architectures,
I'd rather have a clean build of the current state.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- no code changes are expected, just to make sure the patches
apply cleanly with stricter options
prev parent reply other threads:[~2022-07-03 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 15:01 [PR PATCH] " chexum
2022-07-03 17:31 ` paper42
2022-07-03 17:37 ` chexum
2022-07-03 17:51 ` paper42
2022-07-03 18:04 ` chexum
2022-07-03 18:14 ` paper42
2022-07-03 18:25 ` [PR PATCH] [Updated] " chexum
2022-07-03 18:28 ` chexum
2022-07-03 21:23 ` [PR PATCH] [Updated] " paper42
2022-07-03 21:23 ` paper42 [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=20220703212319.AWVeTHVf227aW_zt6SNZzdsBOEUSO_0yAhoVpYX3O0c@z \
--to=paper42@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).