From f485366420578246938ba7d2e6f06a337fb61862 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Wed, 5 Apr 2017 15:22:33 -0700 Subject: fix note about performance Only the rsync:// backend performs incremental pushes. The sftp:// backend is no better than gitception. --- README.rst | 12 ++++++------ debian/changelog | 2 +- 2 files changed, 7 insertions(+), 7 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 `` 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 `` 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 ................. diff --git a/debian/changelog b/debian/changelog index 21545e9..7947fc0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,7 +8,7 @@ git-remote-gcrypt (1.0.2) UNRELEASED; urgency=medium Documentation: * Drop section "Note to users of GnuPG version 2". The issue was a regression in GnuPG 2.x, fixed in version 2.1.16. - * Add a note about performance when pushing to arbitrary git URLs. + * Add a note about performance when not using the rsync:// backend. * Add section containing author and maintainer information. * Add `apt-get` installation instructions, for the benefit of GitHub users. * Other minor edits and formatting changes. -- cgit v1.2.3