part of the participant list. You may use the per-remote version
to sign different remotes using different keys.
+``gcrypt.gpg-args``
+ The contents of this setting are passed as arguments to gpg.
+ E.g. ``--use-agent``.
Environment Variables
=====================
*GCRYPT_FULL_REPACK*
This environment variable forces full repack when pushing.
-*GCRYPT_GPG_ARGS*
- The contents of this environment variable are passed as arguments
- to gpg. E.g. ``export GCRYPT_GPG_ARGS="--use-agent"``.
-
Examples
========
* Taking over as upstream maintainer.
Closes https://github.com/bluss/git-remote-gcrypt/issues/12
* Remove notice about repository format potentially changing.
- * Implement GCRYPT_GPG_ARGS environment variable (Closes: #771011).
+ * Implement gcrypt.gpg-args git config setting (Closes: #771011).
* Respect git config gpg.program if configured.
Thanks Christian Amsüss.
Closes https://github.com/joeyh/git-remote-gcrypt/pull/3
# due to trying to print messages to it, even if a gpg agent is set
# up. --no-tty fixes this.
if [ "x$GPG_AGENT_INFO" != "x" ]; then
- ${GPG} --no-tty "${GCRYPT_GPG_ARGS:-}" "$@"
+ ${GPG} --no-tty "${Conf_gpg_args:-}" "$@"
else
- ${GPG} "${GCRYPT_GPG_ARGS:-}" "$@"
+ ${GPG} "${Conf_gpg_args:-}" "$@"
fi
}
git config --get gcrypt.participants '.+' || :)
Conf_pubish_participants=$(git config --get --bool "remote.$NAME.gcrypt-publish-participants" '.+' ||
git config --get --bool gcrypt.publish-participants || :)
+ Conf_gpg_args=$(git config --get gcrypt.gpg-args '.+' || :)
# Figure out which keys we should encrypt to or accept signatures from
if isnull "$conf_part" || iseq "$conf_part" simple