Re: [Rpm-maint] [RFC] Move all informative messages to stderr by default (ticket #31)

2016-10-25 Thread Panu Matilainen
On 10/25/2016 04:48 PM, Michael Schroeder wrote: On Tue, Oct 25, 2016 at 11:20:14AM +0300, Panu Matilainen wrote: On 10/13/2016 09:41 AM, Panu Matilainen wrote: Rpm has always spewed all sorts of "informative" messages into stdout where it gets mixed up with user requested information such as q

Re: [Rpm-maint] [RFC] Move all informative messages to stderr by default (ticket #31)

2016-10-25 Thread Michael Schroeder
On Tue, Oct 25, 2016 at 11:20:14AM +0300, Panu Matilainen wrote: > On 10/13/2016 09:41 AM, Panu Matilainen wrote: > > Rpm has always spewed all sorts of "informative" messages into stdout > > where it gets mixed up with user requested information such as query > > output, complicating scripts unnec

Re: [Rpm-maint] [RFC] Move all informative messages to stderr by default (ticket #31)

2016-10-25 Thread Panu Matilainen
On 10/13/2016 09:41 AM, Panu Matilainen wrote: Rpm has always spewed all sorts of "informative" messages into stdout where it gets mixed up with user requested information such as query output, complicating scripts unnecessarily and also breaking unix traditions. Make the user-requested output (

[Rpm-maint] [RFC] Move all informative messages to stderr by default (ticket #31)

2016-10-12 Thread Panu Matilainen
Rpm has always spewed all sorts of "informative" messages into stdout where it gets mixed up with user requested information such as query output, complicating scripts unnecessarily and also breaking unix traditions. Make the user-requested output (namely query and verify output) go to stdout by e