git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 1, 2018, 21:55 UTC
Message-ID
<xmqqsh3x69ap.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<24424e55-7fa8-d05b-bc39-e14b4d5abcb6@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 17 quoted lines
>>   Stuck in review?
>>   cf. <20180723203500.231932-1-jonathantanmy@google.com>
>
> This comments on the initial values of 'struct ref_filter' (that are
> not used). All we need is the diff below squashed into "test-reach:
> test commit_contains".
>
>>   cf. <20180723204112.233274-1-jonathantanmy@google.com>
> This comment asks why "parse_commit()" instead of
> "parse_commit_or_die()" but the _or_die() would create a change in
> behavior that is not the purpose of the series.
>>   cf. <CAGZ79kb7tWV=cmboA+nsChAUaiC+fVVM-GBCuWfsypC+-wyaVg@mail.gmail.com>
>
> I just responded to Stefan's comment about sorting. I don't believe
> any change is needed. Some tests output multiple results and the order
> is not defined by the method contract, so 'test-tool reach <verb>'
> will always sort the output (by OID).

Just to let everybody know, there is no point responding to all of "cf. <message>" comments in "What's cooking" report. Because it is *NOT* meant as an exhaustive list of things that need to be fixed, refuting each and every one of them would not make the topic "objection free" anyway. The list of cf.'s are there to have just enough of them to remind me to refrain from merging a topic to 'next' too hurriedly. The discussion thread in the list archive is the authoritative record of the discussion; treat "What's cooking" as my personal note, nothing more.

> (Sorry for the delay. I'm on vacation.)
That's OK, and enjoy your time off.  We are not in a hurry.
Show 17 quoted lines
> Thanks,
> -Stolee
>
> ---
>
> diff --git a/t/helper/test-reach.c b/t/helper/test-reach.c
> index eb21103998..ca30059117 100644
> --- a/t/helper/test-reach.c
> +++ b/t/helper/test-reach.c
> @@ -117,6 +117,7 @@ int cmd__reach(int ac, const char **av)
>     struct ref_filter filter;
>     struct contains_cache cache;
>     init_contains_cache(&cache);
> +    memset(&filter, 0, sizeof(filter));
>
>     if (ac > 2 && !strcmp(av[2], "--tag"))
>         filter.with_commit_tag_algo = 1;
Previous: Derrick StoleeNext: Derrick Stolee
Message 23 of 25 in “What's cooking in git.git (Jul 2018, #03; Wed, 25)”
  1. Junio C HamanoJul 25, 2018
  2. Stefan BellerJul 25, 2018
  3. Junio C HamanoJul 25, 2018
  4. Junio C HamanoJul 26, 2018
  5. Junio C HamanoJul 26, 2018
  6. Junio C HamanoJul 25, 2018
  7. Junio C HamanoJul 25, 2018
  8. Junio C HamanoJul 26, 2018
  9. Оля ТележнаяJul 26, 2018
  10. Junio C HamanoJul 26, 2018
  11. Christian CouderAug 2, 2018
  12. Junio C HamanoAug 2, 2018
  13. Jeff KingJul 26, 2018
  14. Junio C HamanoJul 26, 2018
  15. Jeff KingJul 26, 2018
  16. Ævar Arnfjörð BjarmasonJul 27, 2018
  17. Junio C HamanoJul 27, 2018
  18. range-diff, was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25)Johannes Schindelin, Jul 30, 2018
  19. Junio C HamanoJul 30, 2018
  20. Johannes SchindelinAug 1, 2018
  21. Junio C HamanoAug 1, 2018
  22. ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))Derrick Stolee, Aug 1, 2018
  23. Junio C HamanoAug 1, 2018
  24. ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))Derrick Stolee, Aug 1, 2018
  25. Junio C HamanoAug 1, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.