From: "Christian Walther via GitGitGadget" <email@example.com> To: firstname.lastname@example.org Cc: Christian Walther <email@example.com>, Christian Walther <firstname.lastname@example.org> Subject: [PATCH] doc: mention bigFileThreshold for packing Date: Tue, 09 Feb 2021 19:07:03 +0000 [thread overview] Message-ID: <email@example.com> (raw) From: Christian Walther <firstname.lastname@example.org> Knowing about the core.bigFileThreshold configuration variable is helpful when examining pack file size differences between repositories. Add a reference to it to the manpages a user is likely to read in this situation. Signed-off-by: Christian Walther <email@example.com> --- doc: mention bigFileThreshold for packing I recently spent a lot of time trying to figure out why git repack would create huge packs on some clones of my repository and small ones on others, until I found out about the existence of the core.bigFileThreshold configuration variable, which happened to be set on some and not on others. It would have saved me a lot of time if that variable had been mentioned in the relevant manpages that I was reading, git-repack and git-pack-objects. So this patch adds that. Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-872%2Fcwalther%2Fdeltadoc-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-872/cwalther/deltadoc-v1 Pull-Request: https://github.com/gitgitgadget/git/pull/872 Documentation/git-pack-objects.txt | 4 ++++ Documentation/git-repack.txt | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/Documentation/git-pack-objects.txt b/Documentation/git-pack-objects.txt index 54d715ead137..59150ded4bef 100644 --- a/Documentation/git-pack-objects.txt +++ b/Documentation/git-pack-objects.txt @@ -97,6 +97,10 @@ base-name:: side, because delta data needs to be applied that many times to get to the necessary object. + +Note that delta compression is never used on objects larger than the +`core.bigFileThreshold` configuration variable (see +linkgit:git-config). ++ The default value for --window is 10 and --depth is 50. The maximum depth is 4095. diff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt index 92f146d27dc3..0a7038ec4ad8 100644 --- a/Documentation/git-repack.txt +++ b/Documentation/git-repack.txt @@ -96,6 +96,10 @@ to the new separate pack will be written. affects the performance on the unpacker side, because delta data needs to be applied that many times to get to the necessary object. + +Note that delta compression is never used on objects larger than the +`core.bigFileThreshold` configuration variable (see +linkgit:git-config). ++ The default value for --window is 10 and --depth is 50. The maximum depth is 4095. base-commit: fb7fa4a1fd273f22efcafdd13c7f897814fd1eb9 -- gitgitgadget
next reply other threads:[~2021-02-09 19:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 19:07 Christian Walther via GitGitGadget [this message] 2021-02-09 21:50 ` Junio C Hamano 2021-02-10 21:43 ` Christian Walther 2021-02-10 22:19 ` Junio C Hamano 2021-02-21 13:23 ` [PATCH v2] " Christian Walther via GitGitGadget
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] doc: mention bigFileThreshold for packing' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).