From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] completion: complete refs in multiple steps
Date: Mon, 28 Jan 2019 12:27:42 -0500 [thread overview]
Message-ID: <20190128172742.GA3571@sigill.intra.peff.net> (raw)
In-Reply-To: <20190128172707.GA3050@sigill.intra.peff.net>
On Mon, Jan 28, 2019 at 12:27:07PM -0500, Jeff King wrote:
> Doing that requires actually understanding that the refs are in a list,
> and not formatting each one independently. So I kind of wonder if it
> would be easier to simply have a completion mode in ref-filter.
Er, I meant "a completion mode in for-each-ref", though I think it
largely works out to be the same thing.
-Peff
next prev parent reply other threads:[~2019-01-28 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 9:41 [PATCH/RFC] completion: complete refs in multiple steps Nguyễn Thái Ngọc Duy
2019-01-28 14:38 ` SZEDER Gábor
2019-01-28 17:27 ` Jeff King
2019-01-28 17:27 ` Jeff King [this message]
2019-01-29 0:43 ` Duy Nguyen
2019-01-29 0:47 ` Jeff King
2019-01-29 15:36 ` SZEDER Gábor
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=20190128172742.GA3571@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=szeder.dev@gmail.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.
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).