| commit | d830d395a17a146cfef2aae1c3603907fe3c890b | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Tue, 21 Jul 2015 22:06:43 +0000 (21 15:06 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 21 Jul 2015 22:24:27 +0000 (21 15:24 -0700) | ||
| tree | 4384aa7cebf26beeb2ea882a80493d69b4f2f1e5 | treesnapshot (tar.gz zip) |
| parent | bb3e7b1a5505bae590b0d85a3995a61d6dd82547 | commitdiff |
builtin/send-pack.c: respect user.signingkey
When git-send-pack is exec'ed, as is done by git-remote-http, it
does not read the config, and configured value of user.signingkey is
ignored. Thus it was impossible to specify a signing key over HTTP,
other than the default key in the keyring having a User ID matching
the "Name <email>" format.
This patch at least partially fixes the problem by reading in the GPG
config from within send-pack. It does not address the related problem
of plumbing a value for this configuration option using
`git -c user.signingkey push ...`.
Signed-off-by: Dave Borowitz <dborowitz@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When git-send-pack is exec'ed, as is done by git-remote-http, it
does not read the config, and configured value of user.signingkey is
ignored. Thus it was impossible to specify a signing key over HTTP,
other than the default key in the keyring having a User ID matching
the "Name <email>" format.
This patch at least partially fixes the problem by reading in the GPG
config from within send-pack. It does not address the related problem
of plumbing a value for this configuration option using
`git -c user.signingkey push ...`.
Signed-off-by: Dave Borowitz <dborowitz@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/send-pack.c | diffblobblamehistory |