git-remote-gcrypt - PGP-encrypted git remotes

	Commit message (Collapse)	Author	Age
*	tweak wording in Ulrike's patch	Sean Whitton	2018-07-24
\| \| \| \|	Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
*	Document connectivity issue error message	Ulrike Uhlig	2018-07-24
\| \| \| \| \| \| \| \| \|	Sometimes, git-remote-gcrypt reports 'gcrypt: Repository not found', but this can be due to all sorts of connectivity issues, or even due to ssh-agent using a wrong identity. This should at least be in the docs as it is a very unprecise error message. Signed-off-by: Ulrike Uhlig <ulrike@debian.org>
*	rewrite descriptions of rclone backend in README	Sean Whitton	2018-04-28
\| \| \| \|	Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
*	Add support for several cloud storage remotes using rclone	Beren Minor	2018-04-28
\| \| \| \| \| \| \| \| \| \|	rclone is an open-source command-line too to get and put files to several cloud storage services that aren't supported by rsync. git-remote-gcrypt can now push encrypted repositories to any configured rclone remote using gcrypt::rclone://<rclone-repo>:<folder> URLs. Signed-off-by: Beren Minor <beren.minor+git@gmail.com>
*	add known issues	Sean Whitton	2018-03-09
\|
*	consistent capitalisation for section headers	Sean Whitton	2018-03-09
\|
*	improve first section of manpage	Sean Whitton	2018-03-09
\|
*	add note about non-standard rsync URIs	Sean Whitton	2018-03-09
\|
*	add year I became maintainer	Sean Whitton	2018-03-09
\|
*	avoid comma splice	Sean Whitton	2018-03-09
\|
*	fix note about performance	Sean Whitton	2017-04-05
\| \| \| \| \|	Only the rsync:// backend performs incremental pushes. The sftp:// backend is no better than gitception.
*	tweak install.sh instructions	Sean Whitton	2017-02-19
\|
*	fix typos & formatting errors	Sean Whitton	2017-02-19
\|
*	drop "Note to users of GnuPG version 2"	Sean Whitton	2017-02-19
\|
*	tweak credits section	Sean Whitton	2017-02-19
\|
*	split installation instructions out of quickstart	Sean Whitton	2017-02-19
\|
*	add apt-get installation instructions to README	Sean Whitton	2017-02-19
\|
*	tweak note about performance	Sean Whitton	2017-02-19
\|
*	re-order git-config options	Sean Whitton	2017-02-19
\|
*	drop strongly-worded request for testing	Sean Whitton	2017-02-19
\| \| \| \|	git-remote-gcrypt is stable and in maintenance-mode
*	add authors and maintainers to README	Sean Whitton	2017-02-19
\|
*	add a note about performance	Sean Whitton	2017-02-19
\|
*	add "Note to users of GnuPG version 2" to manpage	Sean Whitton	2016-07-04
\|
*	GCRYPT_GPG_ARGS env var -> gcrypt.gpg-args conf	Sean Whitton	2016-07-04
\|
*	implement GCRYPT_GPG_ARGS	Sean Whitton	2016-01-17
\|
*	changelog entry for version 1.0.0!	Sean Whitton	2016-01-17
\|
*	added gcrypt.publish-participants configuration	Joey Hess	2014-07-15
\| \| \| \|	Fixes https://github.com/blake2-ppc/git-remote-gcrypt/issues/9
*	improve docs	Joey Hess	2013-09-19
\|
*	--check option to see if a repo exists and can be decrypted	Joey Hess	2013-09-19
\| \| \| \| \| \| \| \|	This is to allow programs to determine if a repo uses gcrypt, per #6. Since this program already knows the name of the manifest file and how to download it and decrypt it, it makes sense to do the check here rather than in, eg, git-annex.
*	add remote.<name>.gcrypt-signingkey config	Joey Hess	2013-09-17
\| \| \| \| \| \| \| \| \| \| \| \|	This is needed by git-annex assistant when it sets up a gcrypt repository, to ensure that the gpg key it was asked to use to encrypt the repo is the same key used to sign it. If it's not, pulling from the repo won't work, due to git-remote-gcrypt's "Only accepting signatories" check. The user may have a global user.signingkey setting (I do), but be setting up a different special-purpose key for encrypting their git repo. The git-annex assistant cannot mess with the global value, so needs this to override it.
*	README: Don't mention keyring files, it's not relevant anymore0.20130908	root	2013-03-12
\|
*	Add license header and the text of the GNU GPL	root	2013-03-03
\|
*	Edit wording in README	root	2013-01-21
\|
*	README: Fix to use `remote id`	root	2012-11-29
\|
*	Update license text	root	2012-11-16
\|
*	Fix markup of Repository Format section	root	2013-01-03
\|
*	Edit README	root	2013-01-20
\|
*	Organize the README in a neat way, putting extra info in the Notes chapter	root	2013-02-14
\|
*	Edit the summary of the repository format/process	root	2013-02-14
\|
*	Tone down the development version warnings	root	2013-02-14
\| \| \| \| \|	We have now implemented the usability changes (No fragment in repository URL, and default encrypt-to-self), so no big changes planned.
*	Use a shorter, simpler repo ID since users will see it (occasionally)	root	2013-02-14
\|
*	Update README for remote.<name>.gcrypt-participants and default simple mode	root	2013-02-14
\|
*	Migrate to SHA-256 and implicit repo ID (PARTIAL REPO FORMAT CHANGE)	root	2013-02-14
\| \| \| \| \| \| \| \| \| \|	* local, rsync, ssh, sftp repositories are still compatible * gitception/git backend repositories are not compatible and need to be deleted and recreated * Put manifest in a static location, so we don't need #fragment in the URL * Record repository ID for each remote, and warn if it changes. * Use SHA-256 by default but allow reading SHA-224-identified packfiles * The URL #fragment identifies branch to use when using the git backend
*	Give warning about future format change	root	2013-02-14
\|
*	Allow user to set $GCRYPT_FULL_REPACK to force repack of remote	root	2013-02-14
\|
*	Use rsync for both rsync and ssh access	root	2013-02-14
\|
*	Document the keep field	root	2013-02-14
\|
*	Simplify informational output to emphasize the new repo URL	root	2013-02-14
\|
*	Add ./install.sh to install git-remote-gcrypt and its man page	root	2013-02-14
\|
*	Document manifest fields better	root	2013-02-14
\|