aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.rst
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2020-07-21 20:09:41 -0700
committerSean Whitton <spwhitton@spwhitton.name>2020-07-24 15:35:09 -0700
commit38d6f051ee2c4e6bffb4f6dec55e8853f1eb96f9 (patch)
tree8ed8dfb1b6c2ce96bff707850eea092ffae16fb2 /README.rst
parent323db9eacf7f984727ca84692b98413fc4c1528d (diff)
downloadgit-remote-gcrypt-38d6f051ee2c4e6bffb4f6dec55e8853f1eb96f9.tar.gz
rename new config key
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.rst b/README.rst
index b1f12cb..e7cbfa6 100644
--- a/README.rst
+++ b/README.rst
@@ -97,9 +97,9 @@ The following ``git-config(1)`` variables are supported:
``rsync://`` backend. If the flags are set to a specific remote, the
global flags, if also set, will not be applied for that remote.
-``remote.<name>.gcrypt-force-required``
+``remote.<name>.gcrypt-require-explicit-force-push``
..
-``gcrypt.force-required``
+``gcrypt.require-explicit-force-push``
A known issue is that every git push effectively has a ``--force``.
By default, git-remote-gcrypt will warn the user of this known issue