All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: Junio C Hamano <gitster@pobox.com>,
	Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/1] commit-reach: fix first-parent heuristic
Date: Fri, 19 Oct 2018 15:40:51 -0400	[thread overview]
Message-ID: <c28702fa-f25c-08be-f061-1e5881e82f1a@jeffhostetler.com> (raw)
In-Reply-To: <xmqqk1me3bw0.fsf@gitster-ct.c.googlers.com>



On 10/18/2018 10:31 PM, Junio C Hamano wrote:
> "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 
>> I originally reported this fix [1] after playing around with the trace2
>> series for measuring performance. Since trace2 isn't merging quickly, I
>> pulled the performance fix patch out and am sending it on its own. The only
>> difference here is that we don't have the tracing to verify the performance
>> fix in the test script.
> 
> Thanks for sending this separately.  What's the current status of
> the tracing patch series, by the way?
> 

I'm still working on it. I hope to reroll and submit a new version
next week.  We are currently dogfooding a version of it with our gvfs
users.

Jeff

      reply	other threads:[~2018-10-19 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 17:24 [PATCH 0/1] commit-reach: fix first-parent heuristic Derrick Stolee via GitGitGadget
2018-10-18 17:24 ` [PATCH 1/1] " Derrick Stolee via GitGitGadget
2018-10-19  5:24   ` Junio C Hamano
2018-10-19 12:32     ` Derrick Stolee
2018-10-22  2:29       ` Junio C Hamano
2018-10-19  2:31 ` [PATCH 0/1] " Junio C Hamano
2018-10-19 19:40   ` Jeff Hostetler [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=c28702fa-f25c-08be-f061-1e5881e82f1a@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --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.