From: Sean Whitton <spwhitton@spwhitton.name>
Date: Fri, 9 Mar 2018 18:13:36 +0000 (-0700)
Subject: add known issues
X-Git-Url: https://git.nutra.tk/v1?a=commitdiff_plain;h=958fd5d70c5e47850cd051c491d588a484085caf;p=gamesguru%2Fgit-remote-gcrypt.git

add known issues
---

diff --git a/README.rst b/README.rst
index 8d4b01a..8bcc429 100644
--- a/README.rst
+++ b/README.rst
@@ -216,6 +216,17 @@ encrypted with gcrypt (or could not be accessed).
 Note that this has to fetch the repo contents into the local git
 repository, the same as is done when using a gcrypt repo.
 
+Known issues
+============
+
+Every git push effectively has ``--force``.  Be sure to pull before
+pushing.
+
+git-remote-gcrypt can decide to repack the remote without warning,
+which means that your push can suddenly take significantly longer than
+you were expecting, as your whole history has to be reuploaded.
+This push might fail over a poor link.
+
 See also
 ========
 
diff --git a/debian/changelog b/debian/changelog
index 709a3ba..044e2c8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,7 @@ git-remote-gcrypt (1.0.3-1) UNRELEASED; urgency=medium
   * Add note about non-standard rsync:// URI format.
     Thanks Jane Soko for pointing this out.
   * Improve first section of manpage.
+  * Add "Known issues".
 
  -- Sean Whitton <spwhitton@spwhitton.name>  Thu, 28 Sep 2017 18:32:58 -0700