aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2012-03-23 10:32:33 -0500
committerMax Kellermann <max@duempel.org>2012-03-26 17:32:18 +0200
commitde0f46b947c6016bb72379527ea7af75190b5c4b (patch)
treed8dc7c2a540e4f19c4fa0606ab8e52b15bac744f
parent79eb7623efb3105094dcb77f8688e39b8288155e (diff)
downloadmpd-de0f46b947c6016bb72379527ea7af75190b5c4b.tar.gz
mpd-de0f46b947c6016bb72379527ea7af75190b5c4b.tar.xz
mpd-de0f46b947c6016bb72379527ea7af75190b5c4b.zip
Use g_message and not g_debug when removing song
When adding or updating a song, we get a log message even if debug is not enabled. It seems odd that removing a song shouldn't be done at the same log level; otherwise looking at the log leads you to believe songs are never removed from the library on update. Signed-off-by: Dan McGee <dan@archlinux.org>
-rw-r--r--src/update_remove.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/update_remove.c b/src/update_remove.c
index f7c2342a2..8d60be222 100644
--- a/src/update_remove.c
+++ b/src/update_remove.c
@@ -49,7 +49,7 @@ song_remove_event(void)
assert(removed_song != NULL);
uri = song_get_uri(removed_song);
- g_debug("removing: %s", uri);
+ g_message("removing %s", uri);
g_free(uri);
#ifdef ENABLE_SQLITE