From: Matthew DeVore <matvore@google.com>
To: git@vger.kernel.org
Cc: Matthew DeVore <matvore@google.com>,
sbeller@google.com, git@jeffhostetler.com,
jeffhost@microsoft.com, peff@peff.net, stefanbeller@gmail.com,
jonathantanmy@google.com, gitster@pobox.com, pclouds@gmail.com
Subject: [RFC PATCH 0/3] support for filtering trees and blobs based on depth
Date: Thu, 11 Oct 2018 16:08:59 -0700 [thread overview]
Message-ID: <cover.1539298957.git.matvore@google.com> (raw)
This adds support for depth >0 in the tree:<depth> filter. Before this patch,
only <depth>=0 is supported, which means all trees and blobs are filtered.
The purpose of this is to allow fetching of entire directories in a partial
clone use case. If I do a partial clone of a repo with no objects and then want
to do something like "make" it will be quite slow of we initiate a separate
fetch for every file needed. Alternatively, fetching directories at a time -
as soon as any file in a directory is accessed - is a reasonable approach.
Thank you,
Matthew DeVore (3):
list-objects: support for skipping tree traversal
Documentation/git-rev-list: s/<commit>/<object>/
list-objects-filter: teach tree:# how to handle >0
Documentation/git-rev-list.txt | 21 ++++---
Documentation/rev-list-options.txt | 24 +++++---
builtin/rev-list.c | 2 +-
list-objects-filter-options.c | 6 +-
list-objects-filter-options.h | 1 +
list-objects-filter.c | 52 +++++++++++++---
list-objects-filter.h | 6 ++
list-objects.c | 5 +-
t/t6112-rev-list-filters-objects.sh | 94 +++++++++++++++++++++++++++++
9 files changed, 178 insertions(+), 33 deletions(-)
--
2.19.1.331.ge82ca0e54c-goog
next reply other threads:[~2018-10-11 23:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 23:08 Matthew DeVore [this message]
2018-10-11 23:09 ` [RFC PATCH 1/3] list-objects: support for skipping tree traversal Matthew DeVore
2018-10-14 23:15 ` Junio C Hamano
2018-10-18 0:25 ` Matthew DeVore
2018-10-11 23:09 ` [RFC PATCH 2/3] Documentation/git-rev-list: s/<commit>/<object>/ Matthew DeVore
2018-10-14 23:25 ` Junio C Hamano
2018-10-20 0:03 ` Matthew DeVore
2018-10-22 2:21 ` Junio C Hamano
2018-12-07 22:55 ` Matthew DeVore
2018-12-08 6:24 ` Junio C Hamano
2018-10-11 23:09 ` [RFC PATCH 3/3] list-objects-filter: teach tree:# how to handle >0 Matthew DeVore
2018-10-15 2:31 ` Junio C Hamano
2018-11-08 0:47 ` Matthew DeVore
2018-12-10 23:15 ` Matthew DeVore
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.1539298957.git.matvore@google.com \
--to=matvore@google.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=jonathantanmy@google.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=stefanbeller@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.
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).