diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2020-07-21 20:09:50 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2020-07-24 15:35:38 -0700 |
| commit | ea41d6c979814bc65e468f68e1f8ae33d422fe76 (patch) | |
| tree | 5a6c15544a76dc69f61f6f18ac14f053361ed188 /README.rst | |
| parent | 38d6f051ee2c4e6bffb4f6dec55e8853f1eb96f9 (diff) | |
| download | git-remote-gcrypt-ea41d6c979814bc65e468f68e1f8ae33d422fe76.tar.gz | |
shorten and tweak docs and output
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 10 |
1 files changed, 3 insertions, 7 deletions
@@ -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 ===================== |