On 12/07/2011 11:14 AM, Neil Bothwick wrote:
On Tue, 6 Dec 2011 08:58:23 +0000, Mick wrote:
On Sunday 04 Dec 2011 20:49:55 Neil Bothwick wrote:
On Sun, 4 Dec 2011 15:18:40 +0000, Mick wrote:
But then if there were say 5 ebuilds running in parallel and all
their output printed in the same terminal, it would be almightily
difficult to untangle the spaghetti that may show up in an error?
Which is why setting -j>1 sets wh
Did you mean to finish this message later on, or does "wh" mean
something? o_O
Not only did I mean to finish it, I thought I had. Using --jobs>1 sets
the quiet-build flag
It also sets it if you don't use more than 1 job. As another poster
(Hinnerk) already mentioned, the only way to get the old behavior back
is to use the "--quiet-build=n" option.
