git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aiyee Bee" <shane.880088.supw@gmail.com>
To: <git@vger.kernel.org>
Subject: DEVEL: Help with feature implementation
Date: Mon, 18 Jan 2021 18:06:52 +0000	[thread overview]
Message-ID: <C8MHFL3YJDSF.1GLOUSV7BYS1X@localhost> (raw)

Hello everybody!

I want to implement a feature in git, and I'm looking for some help.

I wanted to add a history-simplification option to rev-list so that it
doesn't simplify away any irrelevant commits if they have multiple
relevant _children_, i.e. when they are the point where two relevant
histories diverge.

Basically the effect I want for --show-forkpoints (named like --show-pulls):
http://ix.io/2Ms6

But it seems there is no existing apparatus in the revision walker for
deciding simplification on basis of *children*, am I correct? Admittedly
my understanding of it is still a WIP, but I don't see anything that
could help.

I was hoping that simply the flag CHILD_SHOWN could be checked, but it
seems that's only set on boundary commits :(

This option would be pretty useful when used with some diffs, to see how
much two forks have diverged. Currently if you use history simplification,
the diffs for both divergent histories will be created against the last
relevant commit instead of the last common ancestor, which creates pretty
useless diffs with a lot of intersection between them.

Are there any viable alternative means to do this that I can explore?

Thanks!

FriendlyNeighborhoodShane

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 18:06 Aiyee Bee [this message]
2021-01-18 18:19 ` DEVEL: Help with feature implementation Antonio Russo
2021-01-18 18:26 ` Derrick Stolee
2021-01-18 19:15   ` Aiyee Bee
2021-01-18 22:54     ` Junio C Hamano
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C8MHFL3YJDSF.1GLOUSV7BYS1X@localhost \
    --to=shane.880088.supw@gmail.com \
    --cc=git@vger.kernel.org \
    /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).