From: Shuqi Liang <cheskaqiqi@gmail.com>
To: git@vger.kernel.org
Cc: Shuqi Liang <cheskaqiqi@gmail.com>, vdye@github.com, gitster@pobox.com
Subject: [PATCH v3 0/3] check-attr: integrate with sparse-index
Date: Tue, 11 Jul 2023 09:30:32 -0400 [thread overview]
Message-ID: <20230711133035.16916-1-cheskaqiqi@gmail.com> (raw)
In-Reply-To: <20230707151839.504494-1-cheskaqiqi@gmail.com>
change against v2:
* add SP at appropriate places
* add in-code comment around magic "adjustment"
Shuqi Liang (3):
attr.c: read attributes in a sparse directory
t1092: add tests for `git check-attr`
check-attr: integrate with sparse-index
attr.c | 47 ++++++++++++--------
builtin/check-attr.c | 3 ++
t/perf/p2000-sparse-operations.sh | 1 +
t/t1092-sparse-checkout-compatibility.sh | 55 ++++++++++++++++++++++++
4 files changed, 87 insertions(+), 19 deletions(-)
Range-diff against v2:
1: 0ff2ab9430 ! 1: 199cc90a5b Enable gitattributes read from sparse directories
@@ Metadata
Author: Shuqi Liang <cheskaqiqi@gmail.com>
## Commit message ##
- Enable gitattributes read from sparse directories
+ attr.c: read attributes in a sparse directory
'git check-attr' cannot currently find attributes of a file within a
sparse directory. This is due to .gitattributes files are irrelevant in
@@ attr.c: static struct attr_stack *read_attr_from_blob(struct index_state *istate
if (!istate)
return NULL;
-- /*
+ /*
- * The .gitattributes file only applies to files within its
- * parent directory. In the case of cone-mode sparse-checkout,
- * the .gitattributes file is sparse if and only if all paths
@@ attr.c: static struct attr_stack *read_attr_from_blob(struct index_state *istate
- * In the case of a sparse index, it is critical that we don't go
- * looking for a .gitattributes file, as doing so would cause the
- * index to expand.
-- */
++ * If the pos value is negative, it means the path is not in the index.
++ * However, the absolute value of pos minus 1 gives us the position where the path
++ * would be inserted in lexicographic order. By subtracting another 1 from this
++ * value (pos = -pos - 2), we find the position of the last index entry
++ * which is lexicographically smaller than the provided path. This would be
++ * the sparse directory containing the path.
+ */
- if (!path_in_cone_mode_sparse_checkout(path, istate))
- return NULL;
+ pos = index_name_pos_sparse(istate, path, strlen(path));
-+ pos = -pos-2;
-+ if (!path_in_cone_mode_sparse_checkout(path, istate) && pos>=0) {
-+ if (!S_ISSPARSEDIR(istate->cache[pos]->ce_mode))
-+ return NULL;
++ pos = - pos - 2;
- buf = read_blob_data_from_index(istate, path, &size);
- if (!buf)
@@ attr.c: static struct attr_stack *read_attr_from_blob(struct index_state *istate
- if (size >= ATTR_MAX_FILE_SIZE) {
- warning(_("ignoring overly large gitattributes blob '%s'"), path);
- return NULL;
+- }
++ if (!path_in_cone_mode_sparse_checkout(path, istate) && 0 <= pos) {
++ if (!S_ISSPARSEDIR(istate->cache[pos]->ce_mode))
++ return NULL;
+
+- return read_attr_from_buf(buf, path, flags);
+ if (strncmp(istate->cache[pos]->name, path, ce_namelen(istate->cache[pos])) == 0) {
+ const char *relative_path = path + ce_namelen(istate->cache[pos]);
+ stack = read_attr_from_blob(istate, &istate->cache[pos]->oid, relative_path, flags);
@@ attr.c: static struct attr_stack *read_attr_from_blob(struct index_state *istate
+ return NULL;
+ }
+ stack = read_attr_from_buf(buf, path, flags);
- }
--
-- return read_attr_from_buf(buf, path, flags);
++ }
+ return stack;
}
2: 835e1176b0 = 2: eefce85083 t1092: add tests for `git check-attr`
3: 672d692e51 = 3: 65c2624504 check-attr: integrate with sparse-index
--
2.39.0
next prev parent reply other threads:[~2023-07-11 13:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 6:48 [PATCH v1 0/3] check-attr: integrate with sparse-index Shuqi Liang
2023-07-01 6:48 ` [PATCH v1 1/3] attr.c: read attributes in a sparse directory Shuqi Liang
2023-07-03 17:59 ` Victoria Dye
2023-07-01 6:48 ` [PATCH v1 2/3] t1092: add tests for `git check-attr` Shuqi Liang
2023-07-03 18:11 ` Victoria Dye
2023-07-01 6:48 ` [PATCH v1 3/3] check-attr: integrate with sparse-index Shuqi Liang
2023-07-03 18:21 ` Victoria Dye
2023-07-07 15:18 ` [PATCH v2 0/3] " Shuqi Liang
2023-07-07 15:18 ` [PATCH v2 1/3] Enable gitattributes read from sparse directories Shuqi Liang
2023-07-07 23:15 ` Junio C Hamano
2023-07-07 15:18 ` [PATCH v2 2/3] t1092: add tests for `git check-attr` Shuqi Liang
2023-07-07 15:18 ` [PATCH v2 3/3] check-attr: integrate with sparse-index Shuqi Liang
2023-07-11 13:30 ` Shuqi Liang [this message]
2023-07-11 13:30 ` [PATCH v3 1/3] attr.c: read attributes in a sparse directory Shuqi Liang
2023-07-11 21:15 ` Junio C Hamano
2023-07-11 22:08 ` Junio C Hamano
2023-07-13 20:22 ` Shuqi Liang
2023-07-13 20:13 ` Shuqi Liang
2023-07-11 21:24 ` Victoria Dye
2023-07-11 13:30 ` [PATCH v3 2/3] t1092: add tests for `git check-attr` Shuqi Liang
2023-07-11 18:52 ` Junio C Hamano
2023-07-11 20:47 ` Victoria Dye
2023-07-11 13:30 ` [PATCH v3 3/3] check-attr: integrate with sparse-index Shuqi Liang
2023-07-11 20:07 ` Junio C Hamano
2023-07-11 16:56 ` [PATCH v3 0/3] " Junio C Hamano
2023-07-18 23:29 ` [PATCH v4 " Shuqi Liang
2023-07-18 23:29 ` [PATCH v4 1/3] t1092: add tests for 'git check-attr' Shuqi Liang
2023-07-20 18:43 ` Victoria Dye
2023-07-18 23:29 ` [PATCH v4 2/3] attr.c: read attributes in a sparse directory Shuqi Liang
2023-07-20 20:18 ` Victoria Dye
2023-08-03 16:22 ` Glen Choo
2023-08-15 8:05 ` Shuqi Liang
2023-07-18 23:29 ` [PATCH v4 3/3] check-attr: integrate with sparse-index Shuqi Liang
2023-08-11 14:22 ` [PATCH v5 0/3] " Shuqi Liang
2023-08-11 14:22 ` [PATCH v5 1/3] t1092: add tests for 'git check-attr' Shuqi Liang
2023-08-11 14:22 ` [PATCH v5 2/3] attr.c: read attributes in a sparse directory Shuqi Liang
2023-08-11 14:22 ` [PATCH v5 3/3] check-attr: integrate with sparse-index Shuqi Liang
2023-08-14 16:24 ` [PATCH v5 0/3] " Victoria Dye
2023-08-14 17:10 ` 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=20230711133035.16916-1-cheskaqiqi@gmail.com \
--to=cheskaqiqi@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).