aboutsummaryrefslogtreecommitdiffstats
path: root/mail/em-composer-utils.c
diff options
context:
space:
mode:
authorMatthew Barnes <mbarnes@redhat.com>2011-07-05 20:16:13 +0800
committerMatthew Barnes <mbarnes@redhat.com>2011-07-05 23:31:01 +0800
commit17127fbee9fd1b0baecb4e305c005d6abbf8d880 (patch)
tree37d0b9ecc37a6685125b2d30567e5b420dacfc59 /mail/em-composer-utils.c
parenta51ea9b9770660531d1d48da4c230e0af118f297 (diff)
downloadgsoc2013-evolution-17127fbee9fd1b0baecb4e305c005d6abbf8d880.tar.gz
gsoc2013-evolution-17127fbee9fd1b0baecb4e305c005d6abbf8d880.tar.zst
gsoc2013-evolution-17127fbee9fd1b0baecb4e305c005d6abbf8d880.zip
Prefer g_seekable_seek() over camel_stream_reset().
When a stream is obviously a file or memory stream (both of which implement the GSeekable interface), use g_seekable_seek() instead of camel_stream_reset(). This is helping me discover if it's safe to remove camel_stream_reset(). We want to eventually move to GIO streams, which have no reset method.
Diffstat (limited to 'mail/em-composer-utils.c')
-rw-r--r--mail/em-composer-utils.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/mail/em-composer-utils.c b/mail/em-composer-utils.c
index 2dcc6872af..c3b5465015 100644
--- a/mail/em-composer-utils.c
+++ b/mail/em-composer-utils.c
@@ -1153,7 +1153,6 @@ traverse_parts (GSList *clues, CamelMimeMessage *message, CamelDataWrapper *cont
if (replace_variables (clues, message, &str)) {
stream = camel_stream_mem_new_with_buffer (str, strlen (str));
- camel_stream_reset (stream, NULL);
camel_data_wrapper_construct_from_stream_sync (
content, stream, NULL, NULL);
g_object_unref (stream);