Remove warning that repack only works on non-promisor packfiles
The git-repack doc clearly states that it *does* operate on promisor packfiles (in a separate partition), with "-a" specified. Presumably the statements here are outdated, as they feature from the first doc in 2017 (and the repack support was added in 2018) Signed-off-by: Tao Klerks <tao@klerks.biz> Reviewed-by: Taylor Blau <me@ttaylorr.com> Acked-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Tao Klerks committed
Jun 2, 2021 at 11:47 UTC
ace6d8e3d66b3559addd2988d5c0eb97d255db95
1 file changed
+1
-5
Documentation/technical/partial-clone.txt
+1
-5
@@ -242,8 +242,7 @@ remote in a specific order.
242
repository and can satisfy all such requests.
243
244
- Repack essentially treats promisor and non-promisor packfiles as 2
245
- distinct partitions and does not mix them. Repack currently only works
246
- on non-promisor packfiles and loose objects.
245
+ distinct partitions and does not mix them.
246
247
- Dynamic object fetching invokes fetch-pack once *for each item*
248
because most algorithms stumble upon a missing object and need to have
@@ -273,9 +272,6 @@ to use those promisor remotes in that order."
272
The user might want to work in a triangular work flow with multiple
273
promisor remotes that each have an incomplete view of the repository.
274
276
-- Allow repack to work on promisor packfiles (while keeping them distinct
277
- from non-promisor packfiles).
278
-
275
- Allow non-pathname-based filters to make use of packfile bitmaps (when
276
present). This was just an omission during the initial implementation.
277