From: Junio C Hamano <gitster@pobox.com>
To: Jeff Hostetler <git@jeffhostetler.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2019, #01; Tue, 5)
Date: Wed, 06 Feb 2019 09:49:58 -0800 [thread overview]
Message-ID: <xmqqk1icrem1.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <b24bfabf-3f79-a290-50b7-5246d870ae12@jeffhostetler.com> (Jeff Hostetler's message of "Wed, 6 Feb 2019 12:18:35 -0500")
Jeff Hostetler <git@jeffhostetler.com> writes:
> On 2/5/2019 6:37 PM, Junio C Hamano wrote:
>> * jh/trace2 (2019-02-01) 15 commits
>> - trace2: add for_each macros to clang-format
>> - trace2: t/helper/test-trace2, t0210.sh, t0211.sh, t0212.sh
>> - trace2:data: add subverb for rebase
>> - trace2:data: add subverb to reset command
>> - trace2:data: add subverb to checkout command
>> - trace2:data: pack-objects: add trace2 regions
>> - trace2:data: add trace2 instrumentation to index read/write
>> - trace2:data: add trace2 hook classification
>> - trace2:data: add trace2 transport child classification
>> - trace2:data: add trace2 sub-process classification
>> - trace2:data: add editor/pager child classification
>> - trace2:data: add trace2 regions to wt-status
>> - trace2: collect Windows-specific process information
>> - trace2: create new combined trace facility
>> - trace2: Documentation/technical/api-trace2.txt
>>
>> A more structured way to obtain execution trace has been added.
>>
>> Still needs some fix-ups.
>> cf. <d91d1d89-5759-2006-7b38-4211db5988af@jeffhostetler.com>
>
> I just pushed a V6 of this series that addresses the hdr-check warning
> in trace2/tr2_tls.h.
Thanks.
prev parent reply other threads:[~2019-02-06 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 23:37 What's cooking in git.git (Feb 2019, #01; Tue, 5) Junio C Hamano
2019-02-06 9:39 ` Denton Liu
2019-02-06 17:49 ` Junio C Hamano
2019-02-06 17:18 ` Jeff Hostetler
2019-02-06 17:49 ` Junio C Hamano [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=xmqqk1icrem1.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@jeffhostetler.com \
--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).