From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] clarify sideband muxing in GIT_TRACE_PACKET
Date: Tue, 1 Sep 2015 16:22:16 -0400 [thread overview]
Message-ID: <20150901202215.GA17370@sigill.intra.peff.net> (raw)
I happened to be debugging push with GIT_TRACE_PACKET today, and got
confused by the mixture of trace from the sideband demuxer and push
itself (details in patch 2/2). This series fixes it by showing a
distinct prefix for the sideband reads.
There's some trickery with start_async() involved, so I've tested it
both with and without NO_PTHREADS set.
[1/2]: run-command: provide in_async query function
[2/2]: pkt-line: show packets in async processes as "sideband"
-Peff
next reply other threads:[~2015-09-01 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 20:22 Jeff King [this message]
2015-09-01 20:22 ` [PATCH 1/2] run-command: provide in_async query function Jeff King
2015-09-01 20:26 ` Jeff King
2015-09-01 22:09 ` Junio C Hamano
2015-09-01 22:17 ` Jeff King
2015-09-01 20:24 ` [PATCH 2/2] pkt-line: show packets in async processes as "sideband" Jeff King
2015-09-01 22:13 ` Junio C Hamano
2015-09-01 22:22 ` Jeff King
2015-09-01 22:23 ` Stefan Beller
2015-09-01 22:26 ` Jeff King
2015-09-01 22:31 ` Stefan Beller
2015-09-01 22:38 ` Jeff King
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=20150901202215.GA17370@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@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).