* Jan Engelhardt wrote on Wed, Mar 11, 2009 at 10:55:02PM CET:
> On Wednesday 2009-03-11 22:43, Ralf Wildenhues wrote:
> >The command line option --silent-rules does the same as the argument
> >`silent' to the AM_INIT_AUTOMAKE macro in configure.ac:
> > AM_INIT_AUTOMAKE([silent])
> >
> >Both enabl
On Wednesday 2009-03-11 22:43, Ralf Wildenhues wrote:
>* Jan Engelhardt wrote on Wed, Mar 11, 2009 at 09:34:20PM CET:
>> On Wednesday 2009-03-11 21:06, Ralf Wildenhues wrote:
>> > Do we want to allow a command line knob (--silent-rules) to turn
>> > off `silent' mode, or do we force developers t
* Jan Engelhardt wrote on Wed, Mar 11, 2009 at 09:34:20PM CET:
> On Wednesday 2009-03-11 21:06, Ralf Wildenhues wrote:
> > Do we want to allow a command line knob (--silent-rules) to turn
> > off `silent' mode, or do we force developers to either touch the
> > AUTOMAKE_OPTIONS variable in Makefi
On Wednesday 2009-03-11 21:06, Ralf Wildenhues wrote:
>* Ralf Wildenhues wrote on Sun, Mar 08, 2009 at 10:46:40AM CET:
>> The current patch still has a couple of warts in that --silent-rules
>> should turn off portability-recursive warnings independently of the
>> command line argument order. Th
* Ralf Wildenhues wrote on Sun, Mar 08, 2009 at 10:46:40AM CET:
> The current patch still has a couple of warts in that --silent-rules
> should turn off portability-recursive warnings independently of the
> command line argument order. This is another reason I don't like this
> addition much: it n
* Ralf Corsepius wrote on Tue, Mar 10, 2009 at 09:02:50AM CET:
> Ralf Wildenhues wrote:
>
>> The patches in the branch should not modify automake's output much if
>> the `silent' option is not used.
>
> %VERBOSE%
Ah, got it. Fixed with this patch. Thanks.
Without `silent' mode, the generated ru
