aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSamuel Tardieu <sam@rfc1149.net>2013-05-23 18:49:08 +0200
committerSamuel Tardieu <sam@rfc1149.net>2013-05-23 18:49:08 +0200
commit3f2ddfa7939ed9b17866f988e964577798c4c11d (patch)
treee83979f5bebabc747470ce49d14460951c122660
parente4720fa138d740b0c2b24ba1864cb3fb730147a1 (diff)
downloadcgeo-3f2ddfa7939ed9b17866f988e964577798c4c11d.zip
cgeo-3f2ddfa7939ed9b17866f988e964577798c4c11d.tar.gz
cgeo-3f2ddfa7939ed9b17866f988e964577798c4c11d.tar.bz2
debug: change log level
Since we know require the unification of the CacheCache with what is in the database, we do not want to scare the user by pretending that a load from the database failed while it is a normal condition for newly encountered geocaches.
-rw-r--r--main/src/cgeo/geocaching/cgData.java2
1 files changed, 1 insertions, 1 deletions
diff --git a/main/src/cgeo/geocaching/cgData.java b/main/src/cgeo/geocaching/cgData.java
index 3a7fcd6..2ef5b27 100644
--- a/main/src/cgeo/geocaching/cgData.java
+++ b/main/src/cgeo/geocaching/cgData.java
@@ -1458,7 +1458,7 @@ public class cgData {
}
if (remaining.size() >= 1) {
- Log.i("cgData.loadCaches(" + remaining.toString() + ") failed");
+ Log.d("cgData.loadCaches(" + remaining.toString() + ") returned no results");
}
return result;
}