All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
	"Jeff King" <peff@peff.net>,
	"Christian Couder" <chriscool@tuxfamily.org>
Subject: [PATCH v5 09/22] Documentation/git-update-index: talk about core.splitIndex config var
Date: Mon,  6 Mar 2017 10:41:50 +0100	[thread overview]
Message-ID: <20170306094203.28250-10-chriscool@tuxfamily.org> (raw)
In-Reply-To: <20170306094203.28250-1-chriscool@tuxfamily.org>

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-update-index.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index 7386c93162..e091b2a409 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -171,6 +171,12 @@ may not support it yet.
 	given again, all changes in $GIT_DIR/index are pushed back to
 	the shared index file. This mode is designed for very large
 	indexes that take a significant amount of time to read or write.
++
+These options take effect whatever the value of the `core.splitIndex`
+configuration variable (see linkgit:git-config[1]). But a warning is
+emitted when the change goes against the configured value, as the
+configured value will take effect next time the index is read and this
+will remove the intended effect of the option.
 
 --untracked-cache::
 --no-untracked-cache::
-- 
2.12.0.206.g74921e51d6.dirty


  parent reply	other threads:[~2017-03-06  9:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  9:41 [PATCH v5 00/22] Add configuration options for split-index Christian Couder
2017-03-06  9:41 ` [PATCH v5 01/22] config: mark an error message up for translation Christian Couder
2017-03-06  9:41 ` [PATCH v5 02/22] t1700: change here document style Christian Couder
2017-03-06  9:41 ` [PATCH v5 03/22] config: add git_config_get_split_index() Christian Couder
2017-03-06  9:41 ` [PATCH v5 04/22] split-index: add {add,remove}_split_index() functions Christian Couder
2017-03-06  9:41 ` [PATCH v5 05/22] read-cache: add and then use tweak_split_index() Christian Couder
2017-03-06  9:41 ` [PATCH v5 06/22] update-index: warn in case of split-index incoherency Christian Couder
2017-03-06  9:41 ` [PATCH v5 07/22] t1700: add tests for core.splitIndex Christian Couder
2017-03-06  9:41 ` [PATCH v5 08/22] Documentation/config: add information " Christian Couder
2017-03-06  9:41 ` Christian Couder [this message]
2017-03-06  9:41 ` [PATCH v5 10/22] config: add git_config_get_max_percent_split_change() Christian Couder
2017-03-06  9:41 ` [PATCH v5 11/22] read-cache: regenerate shared index if necessary Christian Couder
2017-03-06  9:41 ` [PATCH v5 12/22] t1700: add tests for splitIndex.maxPercentChange Christian Couder
2017-03-06  9:41 ` [PATCH v5 13/22] Documentation/config: add splitIndex.maxPercentChange Christian Couder
2017-03-06  9:41 ` [PATCH v5 14/22] sha1_file: make check_and_freshen_file() non static Christian Couder
2017-03-06  9:41 ` [PATCH v5 15/22] read-cache: touch shared index files when used Christian Couder
2017-03-06  9:41 ` [PATCH v5 16/22] config: add git_config_get_expiry() from gc.c Christian Couder
2017-03-06  9:41 ` [PATCH v5 17/22] read-cache: unlink old sharedindex files Christian Couder
2017-03-06  9:41 ` [PATCH v5 18/22] t1700: test shared index file expiration Christian Couder
2017-03-06  9:42 ` [PATCH v5 19/22] read-cache: refactor read_index_from() Christian Couder
2017-03-06  9:42 ` [PATCH v5 20/22] read-cache: use freshen_shared_index() in read_index_from() Christian Couder
2017-03-06  9:42 ` [PATCH v5 21/22] Documentation/config: add splitIndex.sharedIndexExpire Christian Couder
2017-03-06  9:42 ` [PATCH v5 22/22] Documentation/git-update-index: explain splitIndex.* Christian Couder

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=20170306094203.28250-10-chriscool@tuxfamily.org \
    --to=christian.couder@gmail.com \
    --cc=avarab@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=ramsay@ramsayjones.plus.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. 
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.