From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25))
Date: Wed, 1 Aug 2018 16:44:40 -0400 [thread overview]
Message-ID: <24424e55-7fa8-d05b-bc39-e14b4d5abcb6@gmail.com> (raw)
In-Reply-To: <xmqqd0vbt14e.fsf@gitster-ct.c.googlers.com>
On 7/25/2018 6:13 PM, Junio C Hamano wrote:
> * ds/reachable (2018-07-20) 18 commits
> - commit-reach: use can_all_from_reach
> - commit-reach: make can_all_from_reach... linear
> - commit-reach: replace ref_newer logic
> - test-reach: test commit_contains
> - test-reach: test can_all_from_reach_with_flags
> - test-reach: test reduce_heads
> - test-reach: test get_merge_bases_many
> - test-reach: test is_descendant_of
> - test-reach: test in_merge_bases
> - test-reach: create new test tool for ref_newer
> - commit-reach: move can_all_from_reach_with_flags
> - upload-pack: generalize commit date cutoff
> - upload-pack: refactor ok_to_give_up()
> - upload-pack: make reachable() more generic
> - commit-reach: move commit_contains from ref-filter
> - commit-reach: move ref_newer from remote.c
> - commit.h: remove method declarations
> - commit-reach: move walk methods from commit.c
> (this branch uses ds/commit-graph-fsck, jt/commit-graph-per-object-store and sb/object-store-lookup; is tangled with ds/commit-graph-with-grafts.)
>
> The code for computing history reachability has been shuffled,
> obtained a bunch of new tests to cover them, and then being
> improved.
>
> 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).
(Sorry for the delay. I'm on vacation.)
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;
next prev parent reply other threads:[~2018-08-01 20:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 22:13 What's cooking in git.git (Jul 2018, #03; Wed, 25) Junio C Hamano
2018-07-25 22:56 ` Stefan Beller
2018-07-25 23:43 ` Junio C Hamano
2018-07-26 4:14 ` Junio C Hamano
2018-07-26 16:56 ` Junio C Hamano
2018-07-25 23:47 ` Junio C Hamano
2018-07-25 23:48 ` Junio C Hamano
2018-07-26 4:15 ` Junio C Hamano
2018-07-26 6:07 ` Оля Тележная
2018-07-26 16:57 ` Junio C Hamano
2018-08-02 12:41 ` Christian Couder
2018-08-02 18:40 ` Junio C Hamano
2018-07-26 7:24 ` Jeff King
2018-07-26 16:57 ` Junio C Hamano
2018-07-26 20:46 ` Jeff King
2018-07-27 14:28 ` Ævar Arnfjörð Bjarmason
2018-07-27 17:28 ` Junio C Hamano
2018-07-30 13:16 ` range-diff, was " Johannes Schindelin
2018-07-30 15:41 ` Junio C Hamano
2018-08-01 16:01 ` Johannes Schindelin
2018-08-01 19:11 ` Junio C Hamano
2018-08-01 20:44 ` Derrick Stolee [this message]
2018-08-01 21:55 ` ds/reachable (was Re: What's cooking in git.git (Jul 2018, #03; Wed, 25)) Junio C Hamano
2018-08-01 20:53 ` ds/multi-pack-index " Derrick Stolee
2018-08-01 22:13 ` 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=24424e55-7fa8-d05b-bc39-e14b4d5abcb6@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).