From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Emily Shaffer'" <emilyshaffer@google.com>,
"'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: What's cooking in git.git (Jun 2021, #06; Thu, 17)
Date: Fri, 25 Jun 2021 18:26:53 -0400 [thread overview]
Message-ID: <01f101d76a11$36700be0$a35023a0$@nexbridge.com> (raw)
In-Reply-To: <YNZW/zsk93Oi/8uY@google.com>
On June 25, 2021 6:22 PM, Emily Shaffer wrote:
>On Thu, Jun 17, 2021 at 11:55:26AM +0900, Junio C Hamano wrote:
>> * es/trace2-log-parent-process-name (2021-06-09) 1 commit
>> - tr2: log parent process name
>>
>> trace2 logs learned to show parent process name to see in what
>> context Git was invoked.
>>
>> Will merge to 'next'?
>
>I've still not seen much in the way of reviews on this series; mostly Randall and I have been talking about ramifications for
NonStop, but
>those conversations haven't resulted in changes to the series itself.
I'm waiting for the merge to try it in our environment in some real-world situations on the platform. It should be interesting to
see what can be reported and subsequently contributed.
>I think it's fine to merge, but I wrote it, so you shouldn't trust my opinion. :)
>
>We've been running this series internally at Google, though, and it looks like we do want to look up more ancestors than just the
one
>generation, after all. However, I'd prefer to send that as a follow-on patch, compared stalling this topic further.
>
>We do have some early insights from these, though. One interesting observation is that it appears Git is more often invoked via
some
>wrapper than interactively; that's not too surprising given that we have a lot of builders who perform Git operations.
>
>Anyway, all this to say that we've found this trace useful at Google and it's working well for us. Anybody interested in a speedy
review
>would be very welcome.
next prev parent reply other threads:[~2021-06-25 22:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 2:55 What's cooking in git.git (Jun 2021, #06; Thu, 17) Junio C Hamano
2021-06-17 9:38 ` jh/builtin-fsmonitor, was " Johannes Schindelin
2021-06-17 9:40 ` js/subtree-on-windows-fix, " Johannes Schindelin
2021-06-17 12:38 ` Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)) Elijah Newren
2021-06-17 14:19 ` Felipe Contreras
2021-06-17 15:06 ` Elijah Newren
2021-06-17 16:58 ` Felipe Contreras
2021-06-17 14:42 ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-17 23:58 ` brian m. carlson
2021-06-18 0:27 ` Jeff King
2021-06-18 4:28 ` Felipe Contreras
2021-06-19 7:18 ` Junio C Hamano
2021-06-19 17:27 ` Ignoring valid work Felipe Contreras
2021-06-18 4:20 ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-18 16:32 ` Jeff Hostetler
2021-06-25 22:21 ` Emily Shaffer
2021-06-25 22:26 ` Randall S. Becker [this message]
2021-06-28 16:46 ` Jeff Hostetler
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='01f101d76a11$36700be0$a35023a0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=emilyshaffer@google.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.