From: Stan Hu <stanhu@gmail.com>
To: git@vger.kernel.org
Cc: Stan Hu <stanhu@gmail.com>
Subject: [PATCH v2 0/2] completion: refactor and support reftables backend
Date: Wed, 6 Dec 2023 22:06:38 -0800 [thread overview]
Message-ID: <cover.1701928891.git.stanhu@gmail.com> (raw)
In-Reply-To: <20231130202404.89791-1-stanhu@gmail.com>
This patch series addresses the review feedback:
1. Renames the '__git_ref_exists' helper to '__git_pseudoref_exists'.
2. cleans up the commit messages to refer to pseudorefs instead of 'special refs'.
Stan Hu (2):
completion: refactor existence checks for pseudorefs
completion: support pseudoref existence checks for reftables
contrib/completion/git-completion.bash | 43 +++++++++++++++++++++++---
1 file changed, 38 insertions(+), 5 deletions(-)
--
2.42.0
next prev parent reply other threads:[~2023-12-07 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 20:24 [PATCH 0/2] completion: refactor and support reftables backend Stan Hu
2023-11-30 20:24 ` [PATCH 1/2] completion: refactor existence checks for special refs Stan Hu
2023-11-30 20:24 ` [PATCH 2/2] completion: stop checking for reference existence via `test -f` Stan Hu
2023-12-01 7:49 ` Patrick Steinhardt
2023-12-03 13:15 ` [PATCH 1/2] completion: refactor existence checks for special refs Junio C Hamano
2023-12-01 7:49 ` [PATCH 0/2] completion: refactor and support reftables backend Patrick Steinhardt
2023-12-07 6:06 ` Stan Hu [this message]
2023-12-07 6:06 ` [PATCH v2 1/2] completion: refactor existence checks for pseudorefs Stan Hu
2023-12-08 8:24 ` Patrick Steinhardt
2023-12-07 6:06 ` [PATCH v2 2/2] completion: support pseudoref existence checks for reftables Stan Hu
2023-12-19 22:14 ` [PATCH v3 0/2] completion: refactor and support reftables backend Stan Hu
2023-12-19 22:14 ` [PATCH v3 1/2] completion: refactor existence checks for pseudorefs Stan Hu
2024-01-13 21:07 ` SZEDER Gábor
2023-12-19 22:14 ` [PATCH v3 2/2] completion: support pseudoref existence checks for reftables Stan Hu
2023-12-20 0:48 ` [PATCH v3 0/2] completion: refactor and support reftables backend Junio C Hamano
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=cover.1701928891.git.stanhu@gmail.com \
--to=stanhu@gmail.com \
--cc=git@vger.kernel.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.
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.