From: David Vernet <void@manifault.com>
To: konstantin@linuxfoundation.org
Cc: users@linux.kernel.org, tools@linux.kernel.org,
void@manifault.com, kernel-team@fb.com
Subject: [PATCH 1/2] man: Update man page to mention HTTPS_PROXY
Date: Fri, 18 Feb 2022 07:31:27 -0800 [thread overview]
Message-ID: <20220218153128.914071-1-void@manifault.com> (raw)
In-Reply-To: <20220118210808.2158914-1-void@manifault.com>
Certain b4 commands may send requests to https://lore.kernel.org, such
as to fetch a thread of patches as an mbox file. b4 internally uses the
python-requests library to perform these requests, and thus the requests
may be proxied by setting the HTTPS_PROXY environment variable.
The fact that b4 uses the python-requests library is an implementation
detail, so this diff adds a small 'PROXYING REQUESTS' section to the man
page that informs the user that they may use the HTTPS_PROXY environment
variable to enable proxying.
Link: https://lore.kernel.org/all/20220118174144.2445150-1-void@manifault.com/
Signed-off-by: David Vernet <void@manifault.com>
---
man/b4.5.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/man/b4.5.rst b/man/b4.5.rst
index 19e96af..ab12804 100644
--- a/man/b4.5.rst
+++ b/man/b4.5.rst
@@ -321,6 +321,12 @@ Default configuration, with explanations::
# Used when preparing merge messages from cover letters. See shazam-merge-template.example
shazam-merge-template = None
+PROXYING REQUESTS
+-----------------
+Commands making requests to lore may be configured to proxy those requests
+by setting the **HTTPS_PROXY** environment variable, as described in
+https://docs.python-requests.org/en/latest/user/advanced/#proxies.
+
SUPPORT
-------
Please email tools@linux.kernel.org with support requests,
--
2.30.2
next prev parent reply other threads:[~2022-02-18 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 21:08 [PATCH 1/2] man: Update man page to mention HTTPS_PROXY David Vernet
2022-01-18 21:08 ` [PATCH 2/2] man: Update man page to use bold where appropriate David Vernet
2022-02-18 15:31 ` David Vernet [this message]
2022-02-18 15:31 ` David Vernet
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=20220218153128.914071-1-void@manifault.com \
--to=void@manifault.com \
--cc=kernel-team@fb.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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).