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 (Jan 2019, #05; Tue, 29)
Date: Thu, 31 Jan 2019 09:43:45 -0800 [thread overview]
Message-ID: <xmqqftt84t9q.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <2fcac3f7-22be-71fa-eee9-9cc630711029@jeffhostetler.com> (Jeff Hostetler's message of "Wed, 30 Jan 2019 14:07:00 -0500")
Jeff Hostetler <git@jeffhostetler.com> writes:
>> A more structured way to obtain execution trace has been added.
>>
>> Ready?
>
> I'm about to send in a V3 that includes an updated design doc
> and addresses most of the clang-format suggestions.
>
> The CI build reports that my V3 collides with a change
> added yesterday in submodule.c in master. It was added in
> /sb/submodule-recursive-fetch-gets-the-tip.
>
> I'll rebase onto the tip of master and fix it up.
>
> And if there are no comments on my V3, I think it is ready.
Thanks!
next prev parent reply other threads:[~2019-01-31 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:15 What's cooking in git.git (Jan 2019, #05; Tue, 29) Junio C Hamano
2019-01-30 19:07 ` Jeff Hostetler
2019-01-31 17:43 ` Junio C Hamano [this message]
2019-01-31 7:43 ` Denton Liu
2019-01-31 17:49 ` Junio C Hamano
2019-01-31 17:59 ` mk/use-size-t-in-zlib [was: Re: What's cooking in git.git (Jan 2019, #05; Tue, 29)] Thomas Braun
2019-01-31 20:38 ` Torsten Bögershausen
2019-02-04 21:13 ` What's cooking in git.git (Jan 2019, #05; Tue, 29) Thomas Gummerer
2019-02-04 21:30 ` Junio C Hamano
2019-02-05 20:42 ` Thomas Gummerer
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=xmqqftt84t9q.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