From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/6] Some more git config completions
Date: Fri, 2 Jun 2017 00:02:01 +0200 [thread overview]
Message-ID: <CACBZZX6aGkBaQtjKNx09-XEbhXNubOnhJdVXYkNq419wetDvqg@mail.gmail.com> (raw)
In-Reply-To: <20170527062552.13996-1-rikard.falkeborn@gmail.com>
On Sat, May 27, 2017 at 8:25 AM, Rikard Falkeborn
<rikard.falkeborn@gmail.com> wrote:
> Some more completions (from what I could tell, there are probably more
> missing). Please let me know if you prefer them in smaller (or larger)
> batches (or if the patches aren't wanted at all).
This all looks good to me, and I think it would be fine to have
changes like these in bigger batches, they're easy to review.
As an aside from this series, has anyone ever proposed some method of
semi-automatically keeping this up-to-date? Seems we're in a continual
cycle of adding flags/config, forgetting to update this, then updating
it. At least the command-line flags should be easy to parse out in
some test, ditto config variables from config.txt maybe...
next prev parent reply other threads:[~2017-06-01 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 6:25 [PATCH 0/6] Some more git config completions Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 1/6] completion: Add git config gc completions Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 2/6] completion: Add git config core completions Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 3/6] completion: Add git config am.threeWay completion Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 4/6] completion: Add git config advice completions Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 5/6] completion: Add git config credential completions Rikard Falkeborn
2017-05-27 6:25 ` [PATCH 6/6] completion: Add git config credentialCache.ignoreSIGHUP Rikard Falkeborn
2017-06-01 22:02 ` Ævar Arnfjörð Bjarmason [this message]
2017-06-02 0:33 ` [PATCH 0/6] Some more git config completions Junio C Hamano
2017-06-04 18:41 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACBZZX6aGkBaQtjKNx09-XEbhXNubOnhJdVXYkNq419wetDvqg@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=rikard.falkeborn@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).