[libgdata] core: Disable the warning about mismatched kinds

[Philip Withnall <pwithnall src gnome org>]

commit df0fef97fe680062870a01b7d06472eba25c3fb7
Author: Philip Withnall <philip tecnocode co uk>
Date:   Wed May 6 23:23:55 2015 +0100

    core: Disable the warning about mismatched kinds
    
    As explained in the comment in the commit, kind mismatches are a lot
    more common (legitimately), and a lot less avoidable, in the new JSON
    APIs. Give in and stop warning about them.

 gdata/gdata-entry.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/gdata/gdata-entry.c b/gdata/gdata-entry.c
index 7064519..c154d88 100644
--- a/gdata/gdata-entry.c
+++ b/gdata/gdata-entry.c
@@ -925,8 +925,12 @@ gdata_entry_add_category (GDataEntry *self, GDataCategory *category)
                GList *element;
 
                if (klass->kind_term != NULL && g_strcmp0 (gdata_category_get_term (category), 
klass->kind_term) != 0) {
-                       g_warning ("Adding a kind category term, '%s', to an entry of kind '%s'.",
-                                  gdata_category_get_term (category), klass->kind_term);
+                       /* This used to make sense as a warning, but the new
+                        * JSON APIs use a lot of different kinds for very
+                        * highly related JSON schemas, which libgdata uses a
+                        * single class for…so it makes less sense now. */
+                       g_debug ("Adding a kind category term, '%s', to an entry of kind '%s'.",
+                                gdata_category_get_term (category), klass->kind_term);
                }
 
                /* If it is a kind category, remove the entry’s existing kind category to allow the new one