git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Aiyee Bee" <shane.880088.supw@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: DEVEL: Help with feature implementation
Date: Mon, 18 Jan 2021 14:54:42 -0800	[thread overview]
Message-ID: <xmqqzh15j1ot.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <C8MIWAN0N50F.235740W7QGT05@localhost> (Aiyee Bee's message of "Mon, 18 Jan 2021 19:15:43 +0000")

"Aiyee Bee" <shane.880088.supw@gmail.com> writes:

> Maybe a more practical (but still pretty unusual) solution would be adding
> counters to each commit that tell us how many times they have been traversed
> Through various histories?

The "--show-forkpoints" output shown there at http://ix.io/2Ms6
looks interesting.  I think you'd need only 1 bit counter
(i.e. "have we visited it only once, or more than once" bit) for
your purpose?  You traverse from F and Z and the first time you
reach C (probably through the F->E->D->C path), you see no SEEN flag
on the object so leave the new bit alone, and then when the traverse
reaches C again (this time through the Z->Y->C path), while stopping
further traversal because you notice C is already SEEN, you mark it
with the new bit so record that it has been visited at least twice.


  reply	other threads:[~2021-01-18 22:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 18:06 DEVEL: Help with feature implementation Aiyee Bee
2021-01-18 18:19 ` Antonio Russo
2021-01-18 18:26 ` Derrick Stolee
2021-01-18 19:15   ` Aiyee Bee
2021-01-18 22:54     ` Junio C Hamano [this message]
2021-01-18 19:25   ` Aiyee Bee
2021-01-18 19:31   ` Aiyee Bee
2021-01-18 20:58     ` Derrick Stolee
2021-01-19  0:54       ` Antonio Russo
2021-01-19  1:24         ` Junio C Hamano
2021-01-19 14:52           ` Antonio Russo
2021-01-20  2:21             ` Derrick Stolee
2021-01-19  2:39         ` Derrick Stolee
2021-01-19  5:35           ` Aiyee Bee
2021-01-19  5:38           ` Aiyee Bee
2021-01-19 15:13           ` Antonio Russo
  -- strict thread matches above, loose matches on Subject: below --
2021-01-19  5:20 Aiyee Bee
2021-01-19  4:58 Aiyee Bee
2021-01-18 18:00 FriendlyNeighborhoodShane

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=xmqqzh15j1ot.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=shane.880088.supw@gmail.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).