From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2018, #04; Fri, 17)
Date: Mon, 20 Aug 2018 11:19:16 -0700 [thread overview]
Message-ID: <20180820181916.GA31020@aiede.svl.corp.google.com> (raw)
In-Reply-To: <xmqqva88aa0c.fsf@gitster-ct.c.googlers.com>
Junio C Hamano wrote:
> * jh/structured-logging (2018-07-25) 25 commits
> - structured-logging: add config data facility
> - structured-logging: t0420 tests for interacitve child_summary
> - structured-logging: t0420 tests for child process detail events
> - structured-logging: add child process classification
> - structured-logging: add detail-events for child processes
> - structured-logging: add structured logging to remote-curl
> - structured-logging: t0420 tests for aux-data
> - structured-logging: add aux-data for size of sparse-checkout file
> - structured-logging: add aux-data for index size
> - structured-logging: add aux-data facility
> - structured-logging: t0420 tests for timers
> - structured-logging: add timer around preload_index
> - structured-logging: add timer around wt-status functions
> - structured-logging: add timer around do_write_index
> - structured-logging: add timer around do_read_index
> - structured-logging: add timer facility
> - structured-logging: add detail-event for lazy_init_name_hash
> - structured-logging: add detail-event facility
> - structured-logging: t0420 basic tests
> - structured-logging: set sub_command field for checkout command
> - structured-logging: set sub_command field for branch command
> - structured-logging: add session-id to log events
> - structured-logging: add structured logging framework
> - structured-logging: add STRUCTURED_LOGGING=1 to Makefile
> - structured-logging: design document
>
> Will merge to 'next'.
I believe this is under-reviewed (which I certainly share some blame
for). Please hold off and I can look at it today.
prev parent reply other threads:[~2018-08-20 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 22:44 What's cooking in git.git (Aug 2018, #04; Fri, 17) Junio C Hamano
2018-08-18 6:29 ` Duy Nguyen
2018-08-18 6:59 ` Jonathan Nieder
2018-08-20 17:26 ` Junio C Hamano
2018-08-20 18:14 ` Derrick Stolee
2018-08-18 9:34 ` Christian Couder
2018-08-18 11:34 ` Ævar Arnfjörð Bjarmason
2018-08-18 12:54 ` Christian Couder
2018-08-18 11:10 ` Ævar Arnfjörð Bjarmason
2018-08-20 10:23 ` Phillip Wood
2018-08-20 17:44 ` Eric Sunshine
2018-08-20 19:36 ` pw/rebase-i-author-script-fix, was " Johannes Schindelin
2018-08-20 18:11 ` Stefan Beller
2018-08-20 21:32 ` Junio C Hamano
2018-08-20 18:19 ` Jonathan Nieder [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180820181916.GA31020@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).