From: Xin Li <delphij@google.com>
To: git@vger.kernel.org
Cc: Xin Li <delphij@google.com>, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
sandals@crustytoothpaste.net, iankaz@google.com,
Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH v6 0/4] fetch: allow adding a filter after initial clone
Date: Fri, 5 Jun 2020 02:10:00 -0700 [thread overview]
Message-ID: <20200605091004.208668-1-delphij@google.com> (raw)
In-Reply-To: <xmqqk10uzkcd.fsf@gitster.c.googlers.com>
This series of patch makes fetch to allow adding a filter after initial
clone, useful for existing shallow clones as they allow users to see
earlier change histories without downloading all git objects in a regular
--unshallow fetch.
This version of patchset is mostly identical to the v5 draft but splitted
into smaller individual patches.
Please note that the last patch is an incompatible change that would
make extensions stop working for version 0 repositories. Currently,
unknown extensions are silently ignored for version 0, which means the
user may see undesirable result when upgraded to a new Git version.
Xin Li (4):
repository: add a helper function to perform repository format upgrade
fetch: allow adding a filter after initial clone
sparse-checkout: upgrade repository to version 1 when enabling
extension
check_repository_format_gently(): refuse extensions for old
repositories
builtin/fetch.c | 3 ---
builtin/sparse-checkout.c | 2 ++
cache.h | 1 +
list-objects-filter-options.c | 3 ++-
repository.h | 6 +++++
setup.c | 41 +++++++++++++++++++++++++++++---
t/t0410-partial-clone.sh | 23 ++++++++++++++++++
t/t1090-sparse-checkout-scope.sh | 1 -
t/t2404-worktree-config.sh | 4 +++-
t/t5500-fetch-pack.sh | 1 -
t/t5702-protocol-v2.sh | 1 -
11 files changed, 75 insertions(+), 11 deletions(-)
--
2.27.0.278.ge193c7cf3a9-goog
next prev parent reply other threads:[~2020-06-05 9:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 20:00 [PATCH] fetch: allow adding a filter after initial clone Xin Li
2020-05-13 20:43 ` Junio C Hamano
2020-05-13 21:41 ` Xin Li
2020-05-13 22:07 ` Junio C Hamano
2020-05-13 22:18 ` Junio C Hamano
2020-05-13 23:44 ` brian m. carlson
2020-05-28 2:53 ` [PATCH v2 0/1] " Xin Li
2020-05-28 2:54 ` [PATCH v2 1/1] " Xin Li
2020-05-28 3:28 ` Jonathan Nieder
2020-05-28 4:08 ` [PATCH v3] " Xin Li
2020-05-28 15:04 ` [PATCH v2 1/1] " Junio C Hamano
2020-05-28 17:19 ` Jonathan Nieder
2020-05-28 19:12 ` Xin Li
2020-05-28 19:17 ` Jonathan Nieder
2020-05-29 0:04 ` [PATCH v4] " Xin Li
2020-05-29 0:41 ` Junio C Hamano
2020-05-29 18:00 ` Junio C Hamano
2020-05-29 1:01 ` Jonathan Nieder
2020-05-29 6:44 ` [PATCH v5] " Xin Li
2020-05-29 6:54 ` [PATCH v4] " Xin Li
2020-05-29 18:06 ` Junio C Hamano
2020-06-05 9:10 ` Xin Li [this message]
2020-06-05 9:10 ` [PATCH v6 1/4] repository: add a helper function to perform repository format upgrade Xin Li
2020-06-05 19:12 ` Junio C Hamano
2020-06-05 9:10 ` [PATCH v6 2/4] fetch: allow adding a filter after initial clone Xin Li
2020-06-05 19:15 ` Junio C Hamano
2020-06-05 9:10 ` [PATCH v6 3/4] sparse-checkout: upgrade repository to version 1 when enabling extension Xin Li
2020-06-05 19:21 ` Junio C Hamano
2020-06-05 9:10 ` [PATCH v6 4/4] check_repository_format_gently(): refuse extensions for old repositories Xin Li
2020-06-08 16:59 ` 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=20200605091004.208668-1-delphij@google.com \
--to=delphij@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=iankaz@google.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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.