diff options
author | Carl Worth <cworth@cworth.org> | 2009-10-27 16:19:20 -0700 |
---|---|---|
committer | Carl Worth <cworth@cworth.org> | 2009-10-27 16:19:20 -0700 |
commit | 203a717d64864411eb6802c06a5a0ad1cf98e077 (patch) | |
tree | 8dad5abcb17bf07eef0a5e16b99ac4c5ea69145f /notmuch.h | |
parent | 854f82fb91ef9560259e4597d475747e948204d5 (diff) |
notmuch_database_add_message: Do not return a message on failure.
The recent, disastrous failure of "notmuch new" would have been
avoided with this change. The new_command function was basically
assuming that it would only get a message object on success so
wasn't destroying the message in the other cases.
Diffstat (limited to 'notmuch.h')
-rw-r--r-- | notmuch.h | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -252,10 +252,11 @@ notmuch_database_get_timestamp (notmuch_database_t *database, * reference the filename, and will not copy the entire contents of * the file. * - * If 'message' is not NULL, then '*message' will be initialized to a - * message object that can be used for things such as adding tags to - * the just-added message. The user should call - * notmuch_message_destroy when done with the message. + * If 'message' is not NULL, then, on successful return '*message' + * will be initialized to a message object that can be used for things + * such as adding tags to the just-added message. The user should call + * notmuch_message_destroy when done with the message. On any failure + * '*message' will be set to NULL. * * Return value: * |