Re: [PATCH v3 10/12] path-walk: support `tree:0` filter
- From
Taylor Blau <me@ttaylorr.com>
- Date
- May 12, 2026, 01:41 UTC
- Message-ID
- <agKFRV4TjInVOCaO@nand.local>
- In-Reply-To
- <c9efff0ea8d72d2d084957e1b099801b8d8727f3.1778523189.git.gitgitgadget@gmail.com>
On Mon, May 11, 2026 at 06:13:07PM +0000, Taylor Blau via GitGitGadget wrote:
Show 19 quoted lines
> @@ -534,6 +545,18 @@ static int setup_pending_objects(struct path_walk_info *info,
> free(tagged_blobs);
> }
> }
> + if (tagged_trees) {
> + if (tagged_trees->oids.nr) {
> + const char *tagged_tree_path = "/tagged-trees";
> + tagged_trees->type = OBJ_TREE;
> + tagged_trees->maybe_interesting = 1;
> + strmap_put(&ctx->paths_to_lists, tagged_tree_path, tagged_trees);
> + push_to_stack(ctx, tagged_tree_path);
> + } else {
> + oid_array_clear(&tagged_trees->oids);
> + free(tagged_trees);
> + }
> + }
> if (tags) {
> if (tags->oids.nr) {
> const char *tag_path = "/tags";It looks like there is some prior art here for enumerating a sentinel path for "/tags", but I am curious why we did the same for directly-listed trees in the presence of --filter=tree:0.
Thanks, Taylor