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. This is another reason I don't like this >> addition much: it needs more special-casing and complex semantics in >> order to work seamlessly for users. > >Second bug fix of this patch. Pushed to the branch. > >The ugliness of the implementation has been mostly fixed now. So it's >more or less a matter of: > > 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 Makefile.am or the AM_INIT_AUTOMAKE > macro call in configure.ac?
Hm, what is the difference between silent and silent-rules?
