aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.rst
diff options
context:
space:
mode:
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst10
1 files changed, 3 insertions, 7 deletions
diff --git a/README.rst b/README.rst
index e7cbfa6..097c05c 100644
--- a/README.rst
+++ b/README.rst
@@ -100,14 +100,10 @@ The following ``git-config(1)`` variables are supported:
``remote.<name>.gcrypt-require-explicit-force-push``
..
``gcrypt.require-explicit-force-push``
- A known issue is that every git push effectively has a ``--force``.
+ A longstanding bug is that every git push effectively has a ``--force``.
- By default, git-remote-gcrypt will warn the user of this known issue
- when a push is requested without the ``--force`` flag.
-
- If this flag is set to ``true``, git-remote-gcrypt will fail to push,
- as a precaution, unless ``--force`` is passed to git or you prefix your
- refspecs with a '+'.
+ If this flag is set to ``true``, git-remote-gcrypt will refuse to push,
+ unless ``--force`` is passed, or refspecs are prefixed with ``+``.
Environment variables
=====================