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
.................
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.