git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #06; Sat, 30)
Date: Sun, 31 Jan 2021 15:11:34 -0500	[thread overview]
Message-ID: <66be51fb-f40c-5712-8e48-346ca53bd9e8@gmail.com> (raw)
In-Reply-To: <xmqqsg6infev.fsf@gitster.c.googlers.com>

On 1/30/2021 7:00 PM, Junio C Hamano wrote:
> * ds/merge-base-independent (2021-01-28) 3 commits
>  - commit-reach: use heuristic in remove_redundant()
>  - commit-reach: move compare_commits_by_gen
>  - commit-reach: use one walk in remove_redundant()
>  (this branch uses ak/corrected-commit-date; is tangled with ds/chunked-file-api.)
> 
>  The code to implement "git merge-base --independent" was poorly
>  done and was kept from the very beginning of the feature.
> 
>  Will merge to 'next'.

Please hold off until I can push a new version. There were
some meaningful updates to the new algorithm, but also there
is value in the old algorithm when the commit-graph does not
exist (and the heuristic doesn't answer quickly). I'll comment
more in that thread.

Thanks,
-Stolee


  parent reply	other threads:[~2021-01-31 20:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  0:00 What's cooking in git.git (Jan 2021, #06; Sat, 30) Junio C Hamano
2021-01-31  1:42 ` Taylor Blau
2021-01-31 20:50   ` Junio C Hamano
2021-01-31 17:21 ` SZEDER Gábor
2021-01-31 20:52   ` Junio C Hamano
2021-01-31 20:11 ` Derrick Stolee [this message]
2021-01-31 20:53   ` Junio C Hamano
2021-02-01  0:27 ` Ævar Arnfjörð Bjarmason
2021-02-01  1:48   ` Junio C Hamano
2021-02-02 15:54     ` Johannes Schindelin
2021-02-02 20:18       ` Junio C Hamano
2021-02-01 15:51 ` Charvi Mendiratta
2021-02-01 19:48   ` Junio C Hamano
2021-02-02 15:28     ` Charvi Mendiratta
2021-02-03  1:08 ` Đoàn Trần Công Danh
2021-02-03  1:22   ` Junio C Hamano
2021-02-03 22:00     ` Miriam R.
2021-02-04  1:38       ` 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=66be51fb-f40c-5712-8e48-346ca53bd9e8@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 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).