From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-src/update_check: automatically decompress the content
Date: Mon, 17 May 2021 05:57:32 +0200 [thread overview]
Message-ID: <20210517035732.ekEQ5Lz8iarRRuZkjtLdwE2g3cWL1x6pYb2khd8PydM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30590@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/30590#issuecomment-841965572
Comment:
This doesn't just decompress responses, it requests compressed responses. I did a couple of quick checks with a parallel version of `xcheckmypkgs` and received some unexpected `NO VERSION` errors. I'm not sure if this was related to the `--compression` change or rate limiting.
next prev parent reply other threads:[~2021-05-17 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 9:24 [PR PATCH] " unspecd
2021-05-17 3:57 ` ahesford [this message]
2022-05-18 2:09 ` github-actions
2022-06-01 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20210517035732.ekEQ5Lz8iarRRuZkjtLdwE2g3cWL1x6pYb2khd8PydM@z \
--to=ahesford@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).