aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.rst
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2017-04-05 15:22:33 -0700
committerSean Whitton <spwhitton@spwhitton.name>2017-04-05 15:22:33 -0700
commitf485366420578246938ba7d2e6f06a337fb61862 (patch)
tree41376b04001b088dec8e0762c8dec0b8d4c257e1 /README.rst
parent6f880be5021292fb4a060305d5535e1fa2ef144a (diff)
downloadgit-remote-gcrypt-f485366420578246938ba7d2e6f06a337fb61862.tar.gz
fix note about performance
Only the rsync:// backend performs incremental pushes. The sftp:// backend is no better than gitception.
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/README.rst b/README.rst
index 1ceb4da..53a0492 100644
--- a/README.rst
+++ b/README.rst
@@ -135,12 +135,12 @@ Remote ID
remote was re-created.
Performance
- Using an arbitrary `<giturl>` requires uploading the entire
- repository history with each push. If your repository history is
- large or you are pushing over a slow link, consider using either
- the `rsync://` or `sftp://` transports, which perform incremental
- pushes. Note that the latter won't work with a repository hosting
- service like Gitolite, GitHub or GitLab.
+ Using an arbitrary `<giturl>` or an `sftp://` URI requires
+ uploading the entire repository history with each push. If your
+ repository history is large or you are pushing over a slow link,
+ consider using the `rsync://` transport, which performs
+ incremental pushes. Note that the latter won't work with a
+ repository hosting service like Gitolite, GitHub or GitLab.
Repository Format
.................