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: Thu, 29 Oct 2020 12:09:59 -0700 [thread overview]
Message-ID: <xmqqpn507ss8.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqtuuc7wgu.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Thu, 29 Oct 2020 10:50:25 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> I would rather leave it out.
>
> 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.
Actually, I already have an entry in my rerere database to resolve
the merge of these topics to drop the "autoload" suggestion, so I
won't have to do anything other than just queuing the v3 of your
29-patch series.
next prev parent reply other threads:[~2020-10-29 19:10 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 [this message]
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
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=xmqqpn507ss8.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.