From: Shuqi Liang <cheskaqiqi@gmail.com>
To: git@vger.kernel.org
Cc: Shuqi Liang <cheskaqiqi@gmail.com>, vdye@github.com
Subject: [RFC PATCH 0/1] check-attr: integrate with sparse-index
Date: Mon, 27 Feb 2023 00:05:42 -0500 [thread overview]
Message-ID: <20230227050543.218294-1-cheskaqiqi@gmail.com> (raw)
Integrate git check-attr with sparse-index.
Only add 'check-attr pathspec inside sparse definition' yet, just want to see
if the added tests in this patch on the right track.
Also, I have a question about git rev-parse. I read the documentation and wanted to add a test for it,
but I noticed that Derrick already integrated it with sparse-index last year.
Is there anything else I can do with git rev-parse to integrate with sparse-index, or should we just leave it be?
Thanks!
Shuqi Liang (1):
test check-attr pathspec inside sparse definition
builtin/check-attr.c | 3 +++
t/t1092-sparse-checkout-compatibility.sh | 19 +++++++++++++++++++
2 files changed, 22 insertions(+)
base-commit: a38d39a4c50d1275833aba54c4dbdfce9e2e9ca1
--
2.39.0
next reply other threads:[~2023-02-27 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 5:05 Shuqi Liang [this message]
2023-02-27 5:05 ` [RFC PATCH 1/1] check-attr: integrate with sparse-index Shuqi Liang
2023-02-27 17:18 ` Victoria Dye
2023-02-27 17:57 ` Derrick Stolee
2023-02-27 18:51 ` Junio C Hamano
2023-02-28 18:10 ` Shuqi Liang
2023-02-27 17:18 ` [RFC PATCH 0/1] " Victoria Dye
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=20230227050543.218294-1-cheskaqiqi@gmail.com \
--to=cheskaqiqi@gmail.com \
--cc=git@vger.kernel.org \
--cc=vdye@github.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).