aboutsummaryrefslogtreecommitdiffstats
path: root/camel/camel-charset-map.c
diff options
context:
space:
mode:
authorJeffrey Stedfast <fejj@helixcode.com>2000-11-01 08:55:38 +0800
committerJeffrey Stedfast <fejj@src.gnome.org>2000-11-01 08:55:38 +0800
commite0668b4fde4f2800ad223b226fe04b7ccb42c56a (patch)
treeed59a1cfe63526049a48c405945d8676bc5fabb3 /camel/camel-charset-map.c
parenta4768bf6b4c80e7dca746097251702a0d1d8020a (diff)
downloadgsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar.gz
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar.bz2
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar.lz
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar.xz
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.tar.zst
gsoc2013-evolution-e0668b4fde4f2800ad223b226fe04b7ccb42c56a.zip
Shouldn't we be strdup'ing the content? This seems to fix the memory
2000-10-31 Jeffrey Stedfast <fejj@helixcode.com> * mail-format.c (mail_get_message_body): Shouldn't we be strdup'ing the content? This seems to fix the memory corruption problems. (mail_generate_reply): Make sure that the last char in the generated reply text is '\0' (when bodt text doesn't end with a \n, a random char will appear otherwise). svn path=/trunk/; revision=6306
Diffstat (limited to 'camel/camel-charset-map.c')
0 files changed, 0 insertions, 0 deletions