Re: What's cooking in git.git (Sep 2018, #05; Mon, 24)

[Derrick Stolee <stolee@gmail.com>]

On 9/24/2018 6:06 PM, Junio C Hamano wrote:
> * ds/reachable (2018-09-21) 2 commits
>    (merged to 'next' on 2018-09-21 at d4cd62108e)
>   + commit-reach: fix memory and flag leaks
>   + commit-reach: properly peel tags
>
>   Recent update broke the reachability algorithm when refs (e.g.
>   tags) that point at objects that are not commit were involved,
>   which has been fixed.
>   Hotfix for a topic already in 'master'.

Sorry that I took so long to reroll a v4. The changes from v3 to v4 are 
mostly cleanup, so I'll send those as a single commit later, and they 
don't need to be rushed to master as nothing is broken in the version 
you merged.


> * 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.

I've had limited review of this topic that is very exciting (to me). I 
know that last commit is a bit daunting, but I'd love someone to take a 
look.


> * 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?

Just a reminder that we agreed to drop this series.

Thanks,

-Stolee