Fixed bug in gpgme_data_relase_and_get_mem.
Typo fixes.
This commit is contained in:
parent
7ea5674f48
commit
da6f3dc0c5
@ -1,3 +1,7 @@
|
||||
2007-09-11 Werner Koch <wk@g10code.com>
|
||||
|
||||
* gpgme.texi (I/O Callback Example): Typo fix.
|
||||
|
||||
2007-08-07 Werner Koch <wk@g10code.com>
|
||||
|
||||
* gpgme.texi (Verify): Describe chain_model.
|
||||
|
@ -5031,7 +5031,7 @@ monitor these file descriptors for activity and call the appropriate
|
||||
I/O callbacks.
|
||||
|
||||
The following example illustrates how to do that. The example uses
|
||||
locking to show in which way the the callbacks and the event loop can
|
||||
locking to show in which way the callbacks and the event loop can
|
||||
run concurrently. For the event loop, we use a fixed array. For a
|
||||
real-world implementation, you should use a dynamically sized
|
||||
structure because the number of file descriptors needed for a crypto
|
||||
|
@ -1,3 +1,7 @@
|
||||
2007-09-14 Werner Koch <wk@g10code.com>
|
||||
|
||||
* data-mem.c (gpgme_data_release_and_get_mem): Fix tracing bug.
|
||||
|
||||
2007-09-14 Marcus Brinkmann <marcus@g10code.de>
|
||||
|
||||
* gpgme.c (gpgme_release): Call gpgme_sig_notation_clear.
|
||||
|
@ -257,7 +257,14 @@ gpgme_data_release_and_get_mem (gpgme_data_t dh, size_t *r_len)
|
||||
|
||||
gpgme_data_release (dh);
|
||||
|
||||
TRACE_SUC2 ("buffer=%p, len=%u", str, *r_len);
|
||||
if (r_len)
|
||||
{
|
||||
TRACE_SUC2 ("buffer=%p, len=%u", str, *r_len);
|
||||
}
|
||||
else
|
||||
{
|
||||
TRACE_SUC1 ("buffer=%p", str);
|
||||
}
|
||||
return str;
|
||||
}
|
||||
|
||||
|
@ -552,7 +552,7 @@ parse_trust (gpgme_signature_t sig, gpgme_status_code_t code, char *args)
|
||||
{
|
||||
while (*args == ' ')
|
||||
args++;
|
||||
if (!strncmp (args, "cm", 2) && (args[2] == ' ' || !args[2]))
|
||||
if (!strncmp (args, "chain", 2) && (args[2] == ' ' || !args[2]))
|
||||
sig->chain_model = 1;
|
||||
}
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user