summaryrefslogtreecommitdiff
path: root/contrib/credential/gnome-keyring
diff options
context:
space:
mode:
authorLibravatar Martin Ågren <martin.agren@gmail.com>2017-08-07 20:20:46 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-08-07 13:27:21 -0700
commitc4b71a77828ffe7154c2e0bbc5e8a34e843f2f3f (patch)
tree5fc7fc510f643213355c94598a62a8a5c64ad8ad /contrib/credential/gnome-keyring
parentDoc/git-{push,send-pack}: correct --sign= to --signed= (diff)
downloadtgif-c4b71a77828ffe7154c2e0bbc5e8a34e843f2f3f.tar.xz
t5334: document that git push --signed=1 does not work
When accepting booleans as command-line or config options throughout Git, there are several documented synonyms for true and false. However, one particular user is slightly broken: `git push --signed=..` does not understand the integer synonyms for true and false. This is hardly wanted. The --signed option has a different notion of boolean than all other arguments and config options, including the config option corresponding to it, push.gpgSign. Add a test documenting the failure to handle --signed=1. Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/credential/gnome-keyring')
0 files changed, 0 insertions, 0 deletions