From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 1/3] verify_signed_buffer: fix stale comment
Date: Wed, 4 Jan 2012 14:10:56 -0800 [thread overview]
Message-ID: <1325715058-11984-2-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1325715058-11984-1-git-send-email-gitster@pobox.com>
The function used to take an integer flag to specify where the output
should go, but these days we supply a strbuf to receive it.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
gpg-interface.c | 5 +----
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/gpg-interface.c b/gpg-interface.c
index 18630ff..09ab64a 100644
--- a/gpg-interface.c
+++ b/gpg-interface.c
@@ -95,10 +95,7 @@ int sign_buffer(struct strbuf *buffer, struct strbuf *signature, const char *sig
/*
* Run "gpg" to see if the payload matches the detached signature.
- * gpg_output_to tells where the output from "gpg" should go:
- * < 0: /dev/null
- * = 0: standard error of the calling process
- * > 0: the specified file descriptor
+ * gpg_output, when set, receives the diagnostic output from GPG.
*/
int verify_signed_buffer(const char *payload, size_t payload_size,
const char *signature, size_t signature_size,
--
1.7.8.2.340.gd18f0f
next prev parent reply other threads:[~2012-01-04 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 22:10 [PATCH 0/3] More on pulling signed tags Junio C Hamano
2012-01-04 22:10 ` Junio C Hamano [this message]
2012-01-04 22:10 ` [PATCH 2/3] log-tree.c: small refactor in show_signature() Junio C Hamano
2012-01-04 22:10 ` [PATCH 3/3] log-tree: show mergetag in log --show-signature output Junio C Hamano
2012-01-05 0:10 ` [PATCH 0/3] More on pulling signed tags Junio C Hamano
2012-01-05 0:22 ` Junio C Hamano
2012-01-05 0:30 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1325715058-11984-2-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).