Attachment 68580 Details for Bug 55634 – you may want to use a patch like this to test this code

[patch] you may want to use a patch like this to test this code

0001-DO-NOT-COMMIT-hard-code-my-log-path.patch (text/plain), 1.35 KB, created by Will Thompson on 2012-10-15 15:12:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Will Thompson

Created: 2012-10-15 15:12:52 UTC

Size: 1.35 KB

patch

obsolete

>From f9af6feaaa03d6f33cd83b074553adb6ea0bd936 Mon Sep 17 00:00:00 2001
>From: Will Thompson <will.thompson@collabora.co.uk>
>Date: Mon, 15 Oct 2012 16:05:20 +0100
>Subject: [PATCH] DO NOT COMMIT: hard-code my log path
>
>---
> telepathy-logger/log-manager.c     |    2 ++
> telepathy-logger/log-store-gtalk.c |    3 +++
> 2 files changed, 5 insertions(+)
>
>diff --git a/telepathy-logger/log-manager.c b/telepathy-logger/log-manager.c
>index cfd0da0..231a154 100644
>--- a/telepathy-logger/log-manager.c
>+++ b/telepathy-logger/log-manager.c
>@@ -183,6 +183,8 @@ tpl_log_manager_class_init (TplLogManagerClass *klass)
>   object_class->constructor = log_manager_constructor;
>   object_class->finalize = log_manager_finalize;
> 
>+  _tpl_debug_set_flags_from_env ();
>+
>   g_type_class_add_private (object_class, sizeof (TplLogManagerPriv));
> }
> 
>diff --git a/telepathy-logger/log-store-gtalk.c b/telepathy-logger/log-store-gtalk.c
>index 9865f0c..0e75e19 100644
>--- a/telepathy-logger/log-store-gtalk.c
>+++ b/telepathy-logger/log-store-gtalk.c
>@@ -157,6 +157,9 @@ get_mbox_path (
> {
>   TplLogStoreGtalkPriv *priv = self->priv;
> 
>+  if (!tp_strdiff (tp_account_get_path_suffix (account), "gabble/jabber/resiak_40gmail_2ecom0"))
>+    return "/home/wjt/.icedove/3u2k8vf2.default/ImapMail/imap.gmail.com/[Google Mail].sbd/Chats";
>+
>   return g_hash_table_lookup (priv->mbox_paths, account);
> }
> 
>-- 
>1.7.10.4
>

Actions: View | Splinter Review

Attachments on bug 55634: 68580

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.