From: Kyle Meyer <firstname.lastname@example.org> To: Xinglu Chen <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH 0/5] New command for copying public-inbox URLs Date: Sun, 07 Feb 2021 12:35:47 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Kyle Meyer writes: > Hmm, based on dnspython being involved, I guess this happens when b4 > tries to download the thread. piem-b4--get-am-files should take care of > downloading the mbox (mostly to prevent users from needing to configure > b4.midmask), but I guess it falls back to b4 because > piem-b4--get-am-files's call to piem-download-and-decompress fails for > the same reason. But then again, I guess you were probably doing that from notmuch? And in that case, piem-notmuch-mid-to-thread should have produced the thread locally, and there should be no network involved. So maybe this is related to b4's optional attestation checking. Here's how to turn that off: $ git config --global b4.attestation-policy off
next prev parent reply other threads:[~2021-02-07 17:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-07 7:57 Kyle Meyer 2021-02-07 7:57 ` [PATCH 1/5] piem: Add helper to construct message ID link Kyle Meyer 2021-02-07 7:57 ` [PATCH 2/5] piem-dispatch: Add command for copying public-inbox URLs Kyle Meyer 2021-02-07 7:57 ` [PATCH 3/5] piem-copy-mid-url: Add support for browsing url Kyle Meyer 2021-02-07 7:57 ` [PATCH 4/5] piem-copy-mid-url: Allow overriding browse-url-browser-function Kyle Meyer 2021-02-07 7:57 ` [PATCH 5/5] manual: Add section on "copy public-inbox link" functionality Kyle Meyer 2021-02-07 12:38 ` [PATCH 0/5] New command for copying public-inbox URLs Xinglu Chen 2021-02-07 16:57 ` Kyle Meyer 2021-02-07 17:35 ` Kyle Meyer [this message] 2021-02-07 20:25 ` Xinglu Chen
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 List information: https://git.kyleam.com/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/5] New command for copying public-inbox URLs' \ /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
Code repositories for project(s) associated with this inbox: https://git.kyleam.com/piem/ 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).