From 62bd514c8ebef5c7dd6ac2dbc03cf1ef47e450ae Mon Sep 17 00:00:00 2001 From: =?utf8?q?Tim-Philipp=20M=C3=BCller?= Date: Thu, 30 Jul 2015 17:29:25 +0100 Subject: [PATCH] docs: info: remove 0.8 terminology from log level description We don't "iterate" bins or pipelines any more. --- gst/gstinfo.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gst/gstinfo.h b/gst/gstinfo.h index 71cfa41..d4678ac 100644 --- a/gst/gstinfo.h +++ b/gst/gstinfo.h @@ -59,10 +59,10 @@ G_BEGIN_DECLS * An example would be notifications about state changes or receiving/sending * of events. * @GST_LEVEL_LOG: Log messages are messages that are very common but might be - * useful to know. As a rule of thumb a pipeline that is iterating as expected - * should never output anything else but LOG messages. Use this log level to - * log recurring information in chain functions and loop functions, for - * example. + * useful to know. As a rule of thumb a pipeline that is running as expected + * should never output anything else but LOG messages whilst processing data. + * Use this log level to log recurring information in chain functions and + * loop functions, for example. * @GST_LEVEL_TRACE: Tracing-related messages. * Examples for this are referencing/dereferencing of objects. * @GST_LEVEL_MEMDUMP: memory dump messages are used to log (small) chunks of -- 2.7.4