From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: GitHub/GitLab PRs backlog
Date: Sat, 4 Jul 2020 12:57:59 -0700 [thread overview]
Message-ID: <CAH+w=7a2GR2Rkc_HUWJ3sAXF3+NnRjzjNZTQTL4RBUcMaNa6vQ@mail.gmail.com> (raw)
In-Reply-To: <20200703125615.18344b05@tarpaulin.shahaf.local2>
On Fri, Jul 3, 2020 at 5:57 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> completion: Allow specifying directory name for _remote_files
> #53 opened on Apr 20 by insidewhy
> https://github.com/zsh-users/zsh/pull/53
Documentation? How does one use this? Do all the callers need zstyle
update to be able to specify the directory?
> _ssh_hosts: Complete hosts in "Match" directive
> #50 opened on Mar 8 by fumiyas
> https://github.com/zsh-users/zsh/pull/50
> [author pinged us today]
This looks OK to me.
> Add zstd file completion to tar
> #45 opened on Jan 16 by svenstaro • Changes requested
> https://github.com/zsh-users/zsh/pull/45
> [predates zsh-5.8-129-g494f6bcb3, and possibly obsoleted thereby]
The discussion for this one seems not to have been resolved? There's
still only one commit about which there are questions. I don't have a
host where tar supports --zstd to check.
> Fix hexdump command used for mercurial dirstate parsing
> #11 opened on Oct 29, 2016 by reedriley
> https://github.com/zsh-users/zsh/pull/11
> [remaining is confined to Misc/vcs_info-examples]
This needs someone who uses mercurial.
next prev parent reply other threads:[~2020-07-04 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 12:56 Daniel Shahaf
2020-07-03 13:53 ` Daniel Shahaf
2020-07-04 16:16 ` Bart Schaefer
2020-07-05 11:17 ` Daniel Shahaf
2020-07-04 19:57 ` Bart Schaefer [this message]
2020-07-05 11:22 ` Daniel Shahaf
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='CAH+w=7a2GR2Rkc_HUWJ3sAXF3+NnRjzjNZTQTL4RBUcMaNa6vQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).