git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: me@ttaylorr.com, jrnieder@gmail.com,
	Derrick Stolee <dstolee@microsoft.com>
Subject: [PATCH v3 0/2] config: set pack.useSparse=true by default
Date: Fri, 20 Mar 2020 12:38:08 +0000	[thread overview]
Message-ID: <pull.585.v3.git.1584707890.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.585.v2.git.1584707247753.gitgitgadget@gmail.com>

Here is a small patch to convert pack.useSparse to true by default. It's
been released for over a year, so the feature is quite stable. I'm
submitting this now to allow it to cook for a while during the next release
cycle.

UPDATE IN V3: (I'm sorry for the rapid v3, I forgot to push the commit that
included this bit about GIT_TEST_PACK_SPARSE.)

Thanks to Jonathan Nieder pointing out the test implications, I've added a
patch to swap the role of GIT_TEST_PACK_SPARSE to test the other mode.

Thanks, -Stolee

Derrick Stolee (2):
  config: set pack.useSparse=true by default
  pack-objects: flip the use of GIT_TEST_PACK_SPARSE

 Documentation/config/feature.txt   |  3 ---
 Documentation/config/pack.txt      |  4 ++--
 Documentation/git-pack-objects.txt | 10 ++++++----
 builtin/pack-objects.c             |  4 ++--
 repo-settings.c                    |  3 ++-
 t/README                           |  6 +++---
 t/t5322-pack-objects-sparse.sh     |  4 +++-
 7 files changed, 18 insertions(+), 16 deletions(-)


base-commit: 6c85aac65fb455af85745130ce35ddae4678db84
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-585%2Fderrickstolee%2Fpack-use-sparse-v3
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-585/derrickstolee/pack-use-sparse-v3
Pull-Request: https://github.com/gitgitgadget/git/pull/585

Range-diff vs v2:

 1:  60b5cc6f337 = 1:  60b5cc6f337 config: set pack.useSparse=true by default
 -:  ----------- > 2:  908d5c77c96 pack-objects: flip the use of GIT_TEST_PACK_SPARSE

-- 
gitgitgadget

  reply	other threads:[~2020-03-20 12:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  1:58 [PATCH] config: set pack.useSparse=true by default Derrick Stolee via GitGitGadget
2020-03-19 23:13 ` Jonathan Nieder
2020-03-20  0:34   ` Derrick Stolee
2020-03-20 12:27 ` [PATCH v2] " Derrick Stolee via GitGitGadget
2020-03-20 12:38   ` Derrick Stolee via GitGitGadget [this message]
2020-03-20 12:38     ` [PATCH v3 1/2] " Derrick Stolee via GitGitGadget
2020-03-20 12:38     ` [PATCH v3 2/2] pack-objects: flip the use of GIT_TEST_PACK_SPARSE Derrick Stolee via GitGitGadget
2020-03-20 20:43   ` [PATCH v2] config: set pack.useSparse=true by default Junio C Hamano
2020-03-20 21:14     ` Derrick Stolee

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 \
    --in-reply-to=pull.585.v3.git.1584707890.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public 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).