git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Subject: Re: What's cooking in git.git (Jan 2021, #01; Wed, 6)
Date: Fri, 08 Jan 2021 13:35:13 -0800	[thread overview]
Message-ID: <xmqqwnwnglim.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqpn2glcms.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Thu, 07 Jan 2021 12:23:39 -0800")

Junio C Hamano <gitster@pobox.com> writes:

>>> * en/diffcore-rename (2021-01-04) 9 commits
>>>  - diffcore-rename: remove unnecessary duplicate entry checks
>>>  - diffcore-rename: accelerate rename_dst setup
>>>  - diffcore-rename: simplify and accelerate register_rename_src()
>>>  - t4058: explore duplicate tree entry handling in a bit more detail
>>>  - t4058: add more tests and documentation for duplicate tree entry handling
>>>  - diffcore-rename: reduce jumpiness in progress counters
>>>  - diffcore-rename: simplify limit check
>>>  - diffcore-rename: avoid usage of global in too_many_rename_candidates()
>>>  - diffcore-rename: rename num_create to num_destinations
>>>
>>>  File-level rename detection updates.
>>
>> I'm curious again about your workflow and the meanings of your
>> messages.  Here, I'm surprised by the change in date; in [2] you
>> listed it as 2020-12-14.  Do you update the dates when you pull in new
>> versions of the patch series?
>
> These record the committer dates, which is much closer to the date
> the version of the patches were exposed to public testing for the
> first time, and probably is more appropriate than the author date to
> use to judge how long each topic has been "cooked".
>
>> Anyway, I'm not aware of any outstanding requests for this series; I
>> think it's ready to start merging down.  Are there issues you are
>> aware of that you want to see fixed?
>
> Again, just getting overlooked and nobody bothered to ping the
> topic; also I haven't had chance to give these patches serious
> enough reading they deserve yet.

FWIW, I marked the topic to be merged to 'next' after giving this
series a scan and liking it.  I admit that I didn't give too much
tought to the last two steps, though.

Thanks.



  reply	other threads:[~2021-01-08 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 13:38 What's cooking in git.git (Jan 2021, #01; Wed, 6) Junio C Hamano
2021-01-07 18:21 ` Elijah Newren
2021-01-07 20:23   ` Junio C Hamano
2021-01-08 21:35     ` Junio C Hamano [this message]
2021-01-09 22:29   ` Matheus Tavares Bernardino
2021-01-08  4:09 ` Denton Liu

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=xmqqwnwnglim.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    --cc=newren@gmail.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 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 NNTP newsgroup(s).