From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2018, #02; Tue, 13)
Date: Wed, 14 Feb 2018 12:47:55 -0500 [thread overview]
Message-ID: <7259deac-1d9b-fb01-e8dc-3ad7fdd8ecee@gmail.com> (raw)
In-Reply-To: <xmqqy3jvo57n.fsf@gitster-ct.c.googlers.com>
On 2/14/2018 12:23 PM, Junio C Hamano wrote:
> Derrick Stolee <stolee@gmail.com> writes:
>
>> There have been a few "What's cooking" emails since I submitted v1 of
>> "Serialized Git Commit Graph" and it has not appeared with a tracking
>> branch. Is this a mistake, or is it something about the state of the
>> review?
> The latter.
>
> Once I pick up a topic and have it in 'pu', I'd be committing to
> carrying it and keeping it up-to-date, while dealing with possible
> conflicts with other topics. As I do not have infinite bandwidth, I
> try not to chase targets that are still moving too rapidly, which in
> turn means that a hot topic everybody is excited by its goal will
> take more rerolls than other topics before hitting 'pu', because it
> gets more good suggestions and it takes time for its patches to stop
> morphing a lot.
Thanks for clarifying. That makes sense.
> The discussion in the last and current rounds gave me an impression
> that some stuff (e.g. "graph-head") are still likely to change quite
> a lot during the review-response cycle. Is everybody happy with the
> latest set of patches or are there issues raised already in the
> review that are better addressed before we start making it interact
> with other topics in flight?
To avoid causing a tangent in this thread, I'll send a message on the v3
thread summarizing what I plan to do for v4 and ask for consensus on
that approach before I do.
Thanks,
-Stolee
next prev parent reply other threads:[~2018-02-14 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 1:51 What's cooking in git.git (Feb 2018, #02; Tue, 13) Junio C Hamano
2018-02-14 9:36 ` Duy Nguyen
2018-02-14 17:12 ` Junio C Hamano
2018-02-14 14:10 ` Derrick Stolee
2018-02-14 17:23 ` Junio C Hamano
2018-02-14 17:47 ` Derrick Stolee [this message]
2018-02-14 18:11 ` Brandon Williams
2018-02-14 18:21 ` Stefan Beller
2018-02-14 19:07 ` Elijah Newren
2018-02-14 20:16 ` Junio C Hamano
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=7259deac-1d9b-fb01-e8dc-3ad7fdd8ecee@gmail.com \
--to=stolee@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.
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.