From: Lokesh Mandvekar <lsm5@fedoraproject.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: docker completion for zsh
Date: Wed, 20 Aug 2014 16:01:42 -0500 [thread overview]
Message-ID: <20140820210142.GA13727@naruto> (raw)
In-Reply-To: <140820084423.ZM28185@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
On Wed, Aug 20, 2014 at 08:44:23AM -0700, Bart Schaefer wrote:
> On Aug 19, 10:52pm, Lokesh Mandvekar wrote:
> }
> } I was hoping you could include docker completion in the main zsh repo.
>
> I have added this, thanks.
Great, thanks Bart!
--
Lokesh
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-20 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 3:52 Lokesh Mandvekar
2014-08-20 3:59 ` Lokesh Mandvekar
2014-08-20 15:44 ` Bart Schaefer
2014-08-20 21:01 ` Lokesh Mandvekar [this message]
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=20140820210142.GA13727@naruto \
--to=lsm5@fedoraproject.org \
--cc=schaefer@brasslantern.com \
--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).