From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: "Git List" <git@vger.kernel.org>, "Jeff King" <peff@peff.net>,
"Martin Ågren" <martin.agren@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>
Subject: Re: [PATCH v2 6/9] bundle: avoid using the rev_info flag leak_pending
Date: Thu, 28 Dec 2017 13:13:32 -0800 [thread overview]
Message-ID: <xmqq7et6k137.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <5fe3b4c8-e48c-1922-f564-e75c5a354cef@web.de> ("René Scharfe"'s message of "Mon, 25 Dec 2017 18:46:14 +0100")
René Scharfe <l.s.r@web.de> writes:
> The leak_pending flag is so awkward to use that multiple comments had to
> be added around each occurrence. We use it for remembering the
> prerequisites for the bundle. That is easy, though: We have the
> ref_list named "prerequisites" in the header for just that purpose.
Hmph.
> int verify_bundle(struct bundle_header *header, int verbose)
> {
> ...
> struct rev_info revs;
> const char *argv[] = {NULL, "--all", NULL};
> - struct object_array refs;
> struct commit *commit;
> int i, ret = 0, req_nr;
> const char *message = _("Repository lacks these prerequisite commits:");
>
> init_revisions(&revs, NULL);
> for (i = 0; i < p->nr; i++) {
> struct ref_list_entry *e = p->list + i;
> struct object *o = parse_object(&e->oid);
> if (o) {
> o->flags |= PREREQ_MARK;
> add_pending_object(&revs, o, e->name);
> continue;
> }
We mark the prereq objects with PREREQ_MARK and then ...
> if (++ret == 1)
> error("%s", message);
> error("%s %s", oid_to_hex(&e->oid), e->name);
> }
> if (revs.pending.nr != p->nr)
> return ret;
> req_nr = revs.pending.nr;
> setup_revisions(2, argv, &revs, NULL);
... run "rev-list" with "--all" plus these prereq objects, and ...
> ...
> i = req_nr;
> while (i && (commit = get_revision(&revs)))
> if (commit->object.flags & PREREQ_MARK)
> i--;
... let the traversal run until we see all the objects with PREREQ_MARK
set (i.e. those that appear in p->list[]).
> ...
> + for (i = 0; i < p->nr; i++) {
> + struct ref_list_entry *e = p->list + i;
> + struct object *o = parse_object(&e->oid);
> + assert(o); /* otherwise we'd have returned early */
> + if (o->flags & SHOWN)
> + continue;
> + if (++ret == 1)
> + error("%s", message);
> + error("%s %s", oid_to_hex(&e->oid), e->name);
> + }
And then make sure that all of those that appear in p->list[] are
already shown.
Doesn't that mean that these SHOWN and other flags are first given
to the commits at the tip of "--all" refs and propagated down to
those in p->list[]? Would it be sufficient to clear those that can
be reached from them, like the following?
>
> /* Clean up objects used, as they will be reused. */
> - clear_commit_marks_for_object_array(&refs, ALL_REV_FLAGS);
> -
> - object_array_clear(&refs);
> + for (i = 0; i < p->nr; i++) {
> + struct ref_list_entry *e = p->list + i;
> + commit = lookup_commit_reference_gently(&e->oid, 1);
> + if (commit)
> + clear_commit_marks(commit, ALL_REV_FLAGS);
> + }
I do not think the patch in question changes behaviour. The set of
objects the code starts the clearing does not change. So I am more
puzzled by the original than the conversion done with this change.
next prev parent reply other threads:[~2017-12-28 21:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 12:12 [PATCH] revision: introduce prepare_revision_walk_extended() René Scharfe
2017-12-17 10:20 ` Martin Ågren
2017-12-18 15:10 ` Jeff King
2017-12-18 19:18 ` René Scharfe
2017-12-19 11:49 ` Jeff King
2017-12-19 18:33 ` Junio C Hamano
2017-12-20 13:08 ` Jeff King
2017-12-21 18:41 ` René Scharfe
2017-12-24 14:22 ` Jeff King
2017-12-25 17:36 ` René Scharfe
2017-12-25 17:41 ` [PATCH v2 0/9] revision: get rid of the flag leak_pending René Scharfe
2017-12-25 17:43 ` [PATCH v2 1/9] commit: avoid allocation in clear_commit_marks_many() René Scharfe
2018-01-10 7:54 ` Jeff King
2017-12-25 17:44 ` [PATCH v2 2/9] commit: use clear_commit_marks_many() in remove_redundant() René Scharfe
2017-12-25 17:44 ` [PATCH v2 3/9] ref-filter: use clear_commit_marks_many() in do_merge_filter() René Scharfe
2017-12-25 17:44 ` [PATCH v2 4/9] object: add clear_commit_marks_all() René Scharfe
2018-01-10 7:58 ` Jeff King
2018-01-11 18:57 ` René Scharfe
2018-01-12 15:20 ` Jeff King
2017-12-25 17:45 ` [PATCH v2 5/9] bisect: avoid using the rev_info flag leak_pending René Scharfe
2018-01-10 8:07 ` Jeff King
2018-01-11 18:57 ` René Scharfe
2018-01-12 15:23 ` Jeff King
2017-12-25 17:46 ` [PATCH v2 6/9] bundle: " René Scharfe
2017-12-28 21:13 ` Junio C Hamano [this message]
2018-01-10 8:18 ` Jeff King
2017-12-25 17:47 ` [PATCH v2 7/9] checkout: " René Scharfe
2017-12-28 21:24 ` Junio C Hamano
2017-12-25 17:47 ` [PATCH v2 8/9] revision: remove the unused " René Scharfe
2017-12-25 17:48 ` [PATCH v2 9/9] commit: remove unused function clear_commit_marks_for_object_array() René Scharfe
2017-12-28 20:32 ` [PATCH v2 0/9] revision: get rid of the flag leak_pending Junio C Hamano
2018-01-10 8:20 ` Jeff King
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=xmqq7et6k137.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=martin.agren@gmail.com \
--cc=peff@peff.net \
/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).