On Mon, Nov 09, 2009 at 11:21:45PM -0800, Jordan K. Hubbard said:
>
> On Nov 9, 2009, at 4:03 AM, Joshua Root wrote:
>
> > On 2009-11-9 14:13, Jordan K. Hubbard wrote:
> >> On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
> >>
> >>> Should we add the typical steps for producing debug error lo
On Nov 9, 2009, at 4:03 AM, Joshua Root wrote:
> On 2009-11-9 14:13, Jordan K. Hubbard wrote:
>> On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
>>
>>> Should we add the typical steps for producing debug error logs to the
>>> output of the standard trace during a failure?
>>
>> That certai
On 2009-11-9 14:13, Jordan K. Hubbard wrote:
> On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
>
>> Should we add the typical steps for producing debug error logs to the output
>> of the standard trace during a failure?
>
> That certainly sounds like something that should be documented, thou
On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
> Should we add the typical steps for producing debug error logs to the output
> of the standard trace during a failure?
That certainly sounds like something that should be documented, though one
would almost wish to then render that document
On Nov 8, 2009, at 10:03 AM, Jeremy Lavergne wrote:
Should we add the typical steps for producing debug error logs to
the output of the standard trace during a failure?
There are often tickets where people simply place the standard
output and not the debug output. Would supplying the steps
Should we add the typical steps for producing debug error logs to the
output of the standard trace during a failure?
There are often tickets where people simply place the standard output
and not the debug output. Would supplying the steps to do this
directly in the standard reporting help
