From: Derrick Stolee <stolee@gmail.com>
To: Aiyee Bee <shane.880088.supw@gmail.com>, git@vger.kernel.org
Subject: Re: DEVEL: Help with feature implementation
Date: Mon, 18 Jan 2021 13:26:57 -0500 [thread overview]
Message-ID: <60516c8b-adc0-18a5-ac26-b147b1857016@gmail.com> (raw)
In-Reply-To: <C8MHFL3YJDSF.1GLOUSV7BYS1X@localhost>
On 1/18/2021 1:06 PM, Aiyee Bee wrote:
> 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
I think what you really want is --full-history --simplify-merges [1]. This
will show the merges that "fork" the history into parallel tracks where
at least two of them contain interesting commits.
Note that this option is expensive to compute, as it walks every
reachable commit before returning a single result.
Thanks,
-Stolee
[1] https://git-scm.com/docs/git-log#Documentation/git-log.txt---simplify-merges
next prev parent reply other threads:[~2021-01-18 18:28 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 [this message]
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=60516c8b-adc0-18a5-ac26-b147b1857016@gmail.com \
--to=stolee@gmail.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.
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).