git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Remove warning that repack only works on non-promisor packfiles

From
Tao Klerks via GitGitGadget <gitgitgadget@gmail.com>
Date
Jun 2, 2021, 11:47 UTC
Message-ID
<pull.968.git.1622634446643.gitgitgadget@gmail.com>
From: Tao Klerks <tao@klerks.biz>

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>
---
    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)
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-968%2FTaoK%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-968/TaoK/patch-1-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/968
 Documentation/technical/partial-clone.txt | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/Documentation/technical/partial-clone.txt b/Documentation/technical/partial-clone.txt
index 0780d30caca6..a0dd7c66f247 100644
--- a/Documentation/technical/partial-clone.txt
+++ b/Documentation/technical/partial-clone.txt
@@ -242,8 +242,7 @@ remote in a specific order.
   repository and can satisfy all such requests.
 
 - Repack essentially treats promisor and non-promisor packfiles as 2
-  distinct partitions and does not mix them.  Repack currently only works
-  on non-promisor packfiles and loose objects.
+  distinct partitions and does not mix them.
 
 - Dynamic object fetching invokes fetch-pack once *for each item*
   because most algorithms stumble upon a missing object and need to have
@@ -273,9 +272,6 @@ to use those promisor remotes in that order."
 The user might want to work in a triangular work flow with multiple
 promisor remotes that each have an incomplete view of the repository.
 
-- Allow repack to work on promisor packfiles (while keeping them distinct
-  from non-promisor packfiles).
-
 - Allow non-pathname-based filters to make use of packfile bitmaps (when
   present).  This was just an omission during the initial implementation.
 

base-commit: ed125c4f07ba69c53c9f4d74ff395a4bf7854ea7
-- 
gitgitgadget
Next: Taylor Blau
Message 1 of 4 in “Remove warning that repack only works on non-promisor packfiles”
  1. Remove warning that repack only works on non-promisor packfilesTao Klerks via GitGitGadget, Jun 2, 2021
  2. Taylor BlauJun 2, 2021
  3. Jonathan TanJun 3, 2021
  4. Junio C HamanoJun 4, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.