After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 650882 - use stdout instead of stderr for informational messages
use stdout instead of stderr for informational messages
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
2.28.x
Other All
: Normal minor
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-05-23 15:49 UTC by Antoine Jacoutot
Modified: 2011-05-27 22:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stderr -> stdout (625 bytes, patch)
2011-05-23 15:49 UTC, Antoine Jacoutot 		none Details | Review

Description Antoine Jacoutot 2011-05-23 15:49:33 UTC 
Created attachment 188391 [details] [review]
stderr -> stdout

Hi.

Is there any reason glib-compile-schemas output the followings to stderr instead of stdout. IMHO these are just informative messages but they are not errors nor critical in any way:
"No schema files found: doing nothing."
"No schema files found: removed existing output file."

I guess it would make more sense to let them use stdout and it will allow to redirect stdout to /dev/null for people who may want it (currently if you don't want to see these messages, you have to 2>/dev/null which is not really nice in case you get a real error).

Patch attached.
Thoughts?
Comment 1 Matthias Clasen 2011-05-27 22:32:10 UTC 
Makes sense to me