From: Xinglu Chen <public@yoctocell.xyz>
To: Kyle Meyer <kyle@kyleam.com>, piem@inbox.kyleam.com
Subject: Re: [PATCH 0/5] New command for copying public-inbox URLs
Date: Sun, 07 Feb 2021 13:38:02 +0100 [thread overview]
Message-ID: <87sg6859zp.fsf@yoctocell.xyz> (raw)
In-Reply-To: <20210207075738.8752-1-kyle@kyleam.com>
On Sun, Feb 07 2021, Kyle Meyer wrote:
> Prompted by Xinglu's recent notmuch-show-stash-mlarchive-link addition
> (<https://inbox.kyleam.com/piem/878s81kd8u.fsf@kyleam.com>), this
> series adds a command, piem-copy-mid-url, that can copy the URL in any
> buffer with an associated message ID and inbox (which I'll mostly find
> useful in Gnus).
>
> The last patch updates the manual to mention piem-copy-mid-url as well
> as the piem-aware notmuch-show-stash-mlarchive-link.
>
> [1/5] piem: Add helper to construct message ID link
> [2/5] piem-dispatch: Add command for copying public-inbox URLs
> [3/5] piem-copy-mid-url: Add support for browsing url
> [4/5] piem-copy-mid-url: Allow overriding browse-url-browser-function
> [5/5] manual: Add section on "copy public-inbox link" functionality
This looks good to me. But when I try to apply the patchset with
`piem-b4-am-from-mid` it returns an error (I only pasted the last part):
File "/nix/store/c3rw242zljng83r21jbpczwg54g97d5l-python3.8-dnspython-2.0.0/lib/python3.8/site-packages/dns/resolver.py", line 598, in next_nameserver
raise NoNameservers(request=self.request, errors=self.errors)
dns.resolver.NoNameservers: All nameservers failed to answer the query key1._domainkey.kyleam.com. IN TXT: Server 192.168.1.1 UDP port 53 answered ; Server 192.168.1.1 TCP port 53 answered [Errno 111] Connection refused
This doesn’t happen if i try the same thing on the notmuch archive [1].
Are you able to reproduce this?
Sorry for the extra noise.
[1]: https://yhetil.org/notmuch/20210205132654.3258292-1-david@tethera.net
next prev parent reply other threads:[~2021-02-07 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 7:57 [PATCH 0/5] New command for copying public-inbox URLs 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 ` Xinglu Chen [this message]
2021-02-07 16:57 ` [PATCH 0/5] New command for copying public-inbox URLs Kyle Meyer
2021-02-07 17:35 ` Kyle Meyer
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 \
--in-reply-to=87sg6859zp.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=kyle@kyleam.com \
--cc=piem@inbox.kyleam.com \
/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.
Code repositories for project(s) associated with this public 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).