From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: [child0:1694] <timed out>
Date: Fri, 15 Aug 2014 14:15:26 -0400 [thread overview]
Message-ID: <20140815181526.GA28839@redhat.com> (raw)
In-Reply-To: <53EE4B19.4000305@gmx.de>
On Fri, Aug 15, 2014 at 08:02:01PM +0200, Toralf Förster wrote:
> > > With latest git tree I do get now a lot of lines like :
> > >
> > > [child0:1694] <timed out>
> >
> /me wonders if dfdb9560d brought this message to my eyes ?
ah, yes, quite likely. I need to go over a lot of that loglevel code
again at some point, there are a few problems with it. Kinda low down
on my list right now, but I'll get to it before the next tarball
release.
> Well for the stack trace feature I've to wait till it is implemented - Richard Weinberger told me that there#S a guy just doing it.
Bah, I thought this was ubiquitous by now..
Dave
prev parent reply other threads:[~2014-08-15 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 17:17 [child0:1694] <timed out> Toralf Förster
2014-08-14 22:27 ` Dave Jones
2014-08-15 18:02 ` Toralf Förster
2014-08-15 18:15 ` Dave Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140815181526.GA28839@redhat.com \
--to=davej@redhat.com \
--cc=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).