From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2018, #01; Wed, 10)
Date: Thu, 11 Oct 2018 07:16:10 -0400 [thread overview]
Message-ID: <dfa79ba2-0dba-1d74-1a81-543902d20bef@gmail.com> (raw)
In-Reply-To: <xmqq8t36mk4t.fsf@gitster-ct.c.googlers.com>
On 10/10/2018 1:43 AM, Junio C Hamano wrote:
>
> * ds/reachable-topo-order (2018-09-21) 7 commits
> - revision.c: refactor basic topo-order logic
> - revision.h: add whitespace in flag definitions
> - commit/revisions: bookkeeping before refactoring
> - revision.c: begin refactoring --topo-order logic
> - test-reach: add rev-list tests
> - test-reach: add run_three_modes method
> - prio-queue: add 'peek' operation
>
> The revision walker machinery learned to take advantage of the
> commit generation numbers stored in the commit-graph file.
>
> What's the status of this topic?
I've reached out for review, especially on the rather large patch
"revision.c: refactor basic topo-order logic" but have received no
messages about it. I don't think anyone has even done a cursory style
review.
I really think that this is a valuable topic, and it would be nice to
have in 2.20, but I'm not pushing to merge something that no one has
reviewed.
> * ds/format-commit-graph-docs (2018-08-21) 2 commits
> - commit-graph.txt: improve formatting for asciidoc
> - Docs: Add commit-graph tech docs to Makefile
>
> Design docs for the commit-graph machinery is now made into HTML as
> well as text.
>
> Will discard.
> I am inclined to drop these, as I do not see much clarity in HTML
> output over the text source. Opinions?
These have been marked for discard for a few weeks. I agree they should
be discarded.
Thanks,
-Stolee
next prev parent reply other threads:[~2018-10-11 11:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 5:43 What's cooking in git.git (Oct 2018, #01; Wed, 10) Junio C Hamano
2018-10-10 7:59 ` Ævar Arnfjörð Bjarmason
2018-10-10 15:06 ` Jeff King
2018-10-10 12:57 ` builtin stash/rebase, was " Johannes Schindelin
2018-10-10 13:19 ` Junio C Hamano
2018-10-11 2:18 ` Junio C Hamano
2018-10-10 13:04 ` js/mingw-wants-vista-or-above, " Johannes Schindelin
2018-10-10 13:13 ` Junio C Hamano
2018-10-10 13:58 ` Phillip Wood
2018-10-11 1:54 ` Junio C Hamano
2018-10-11 22:40 ` Junio C Hamano
2018-10-11 22:59 ` [PATCH] diff.c: die on unknown color-moved ws mode Stefan Beller
2018-10-11 23:01 ` Stefan Beller
2018-10-12 1:22 ` Junio C Hamano
2018-10-11 23:06 ` What's cooking in git.git (Oct 2018, #01; Wed, 10) Stefan Beller
2018-10-12 0:51 ` Junio C Hamano
2018-10-12 9:59 ` Phillip Wood
2018-10-12 13:36 ` Junio C Hamano
2018-10-16 13:38 ` Phillip Wood
2018-10-16 17:13 ` Stefan Beller
2018-10-10 14:18 ` Thomas Gummerer
2018-10-11 1:40 ` Junio C Hamano
2018-10-10 18:51 ` `--rebase-merges' still failing badly Michael Witten
2018-10-10 19:00 ` Michael Witten
2018-10-10 23:01 ` Junio C Hamano
2018-10-11 2:44 ` Michael Witten
2018-10-12 9:11 ` Johannes Schindelin
2018-10-10 18:55 ` What's cooking in git.git (Oct 2018, #01; Wed, 10) Stefan Beller
2018-10-11 2:00 ` Junio C Hamano
2018-10-10 20:38 ` Tim Schumacher
2018-10-10 21:25 ` Johannes Sixt
2018-10-11 1:53 ` Junio C Hamano
2018-10-11 11:16 ` Derrick Stolee [this message]
2018-10-14 12:21 ` Duy Nguyen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfa79ba2-0dba-1d74-1a81-543902d20bef@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).