On Mon, August 24, 2015 21:25:08 Michael Pyne wrote:
> This is indeed almost certainly my breakage (oops!) but where did this email
> go to? I hope I didn't flag it read by accident because I don't remember
> seeing it yet.
Never mind, found them. Are there "brown paper bag emails"? The email I'm
On Mon, August 24, 2015 11:42:21 Patrick Eigensatz wrote:
> Using git bisect and the information of Siddhartha I got this causing the
> "1" output:
>
> Milian Wolff schrieb am Mo., 24. Aug. 2015 um 13:07 Uhr:
> > On Monday, August 24, 2015 11:10:52 AM CEST Kevin Funk wrote:
> > > Heya guys,
> > >
Using git bisect and the information of Siddhartha I got this causing the
"1" output:
commit 94a1a1f5e2333ef8406789c6942a4976e923fd55
Author: Michael Pyne
Date: Sat Aug 8 23:20:00 2015 -0400
ui: Minor overhaul in way we display build command output.
Should be a bit faster, but major goa
On Monday, August 24, 2015 11:10:52 AM CEST Kevin Funk wrote:
> Heya guys,
>
> A few revisions ago, kdesrc-buildrc had that "hidden" --debug option that
> allowed me to see compile output right away. This no longer works but I'd
> like to have the feature back, one way or the other.
>
> So, is it
On 24 August 2015 at 14:40, Kevin Funk wrote:
> Heya guys,
>
> A few revisions ago, kdesrc-buildrc had that "hidden" --debug option that
> allowed me to see compile output right away. This no longer works but I'd like
> to have the feature back, one way or the other.
Seems to be a bug in the kdes
Heya guys,
A few revisions ago, kdesrc-buildrc had that "hidden" --debug option that
allowed me to see compile output right away. This no longer works but I'd like
to have the feature back, one way or the other.
So, is it possible atm? I'd really like to have --verbose print command
invocation
