From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Лёша Огоньков" <lesha.ogonkov@gmail.com>,
"Stefan Haller" <lists@haller-berlin.de>,
"Alexey via GitGitGadget" <gitgitgadget@gmail.com>,
Git <git@vger.kernel.org>
Subject: Re: [PATCH] Fix zsh installation instructions
Date: Mon, 02 Nov 2020 14:37:17 -0800 [thread overview]
Message-ID: <xmqq7dr3s7vm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAMP44s1+bJMrmJWeAQx18S-=spoKb0BmzWyJ4WgzuE+rNuf0cg@mail.gmail.com> (Felipe Contreras's message of "Mon, 2 Nov 2020 14:49:51 -0600")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> This should be enough:
> ---
> autoload -U compinit && compinit
> ---
>
>> Makes sense. Instead of adjusting my rerere database for that,
>> ejecting lo/zsh-completion topic would be easier---what the other
>> half of that patch does is already in your 29-patch series.
Your 29-patch series is now in 'next'; I have this feeing that
nobody around here would offer any meaningful reviews on it, so it
may graduate sooner than the usual topics.
Thanks.
next prev parent reply other threads:[~2020-11-02 22:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 10:51 [PATCH] Fix zsh installation instructions Alexey via GitGitGadget
2020-07-06 22:42 ` Junio C Hamano
2020-10-14 15:10 ` Stefan Haller
2020-10-16 17:06 ` Junio C Hamano
2020-10-25 3:29 ` Felipe Contreras
2020-10-27 8:29 ` Stefan Haller
2020-10-27 8:32 ` Stefan Haller
2020-10-27 8:59 ` Лёша Огоньков
2020-10-27 20:00 ` Junio C Hamano
2020-10-28 1:45 ` Felipe Contreras
2020-10-29 17:50 ` Junio C Hamano
2020-10-29 19:09 ` Junio C Hamano
2020-11-02 20:49 ` Felipe Contreras
2020-11-02 20:54 ` Felipe Contreras
2020-11-03 1:02 ` Junio C Hamano
2020-11-02 22:37 ` Junio C Hamano [this message]
2020-10-28 1:31 ` Felipe Contreras
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=xmqq7dr3s7vm.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=lesha.ogonkov@gmail.com \
--cc=lists@haller-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.