From: Antonio Russo <antonio.e.russo@gmail.com>
To: Philip Oakley <philipoakley@iee.email>, git-ml <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH v2] Teach git-rev-list --simplify-forks
Date: Wed, 29 Apr 2020 07:04:41 -0600 [thread overview]
Message-ID: <ceeb706d-83ad-c994-121d-d66724d82a49@gmail.com> (raw)
In-Reply-To: <eda71f1e-b883-82c3-72f2-dc5221804c4b@iee.email>
On 4/29/20 4:08 AM, Philip Oakley wrote:
>> +--simplify-forks::
>> + Convert the commit graph into a spanning subgraph produced by a
>> + depth-first-search of the history graph, searching the leftmost
>> + parent first, and discarding edges to commits already visited.
>> + Useful with `--graph` to visualize repositories with many merges
>> + when you are interested in was added to master, and not when the
>> + branch was last rebased.
>
> Does this also need to actually mention that it effectively discard
> edges to fork points, as per the option name?. No rebasing required for
> it to be useful.
> s/when/where/
> "...and not where the branch was last rebased or forked from." - not
> great but actually mentions the option.
>
> --
> Philip
Good point. More generally, my description of the option is not very
useful unless you already basically understand what it's doing.
How about:
> --simplify-forks::
> Omits the parent relationship of the first commit of merged branches.
> Effectively discards all information about the fork point of merged
> branches. It does so by converting the commit graph into a
> spanning subgraph produced by a depth-first-search of the history
> graph, searching the leftmost parent first, and discarding edges
> to commits already visited. Useful with `--graph` to visualize
> repositories with many merges when you are most interested in
> when branches were merged.
Antonio
next prev parent reply other threads:[~2020-04-29 13:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 5:07 [PATCH] Teach git-rev-list --simplify-forks Antonio Russo
2020-04-27 10:55 ` Derrick Stolee
2020-04-28 12:49 ` Antonio Russo
2020-04-28 14:11 ` Derrick Stolee
2020-04-29 8:01 ` [PATCH v2] " Antonio Russo
2020-04-29 10:08 ` Philip Oakley
2020-04-29 13:04 ` Antonio Russo [this message]
2020-04-29 13:12 ` Derrick Stolee
2020-05-01 14:13 ` Antonio Russo
2020-05-01 15:44 ` Derrick Stolee
2020-05-01 14:21 ` [PATCH 1/3 v3] Clean up t6016-rev-list-graph-simplify-history Antonio Russo
2020-05-01 17:10 ` Junio C Hamano
2020-05-02 15:27 ` Antonio Russo
2020-05-01 14:22 ` [PATCH 2/3 v3] Teach git-rev-list --ignore-merge-bases Antonio Russo
2020-05-02 13:25 ` Johannes Sixt
2020-05-02 14:21 ` Antonio Russo
2020-05-01 14:23 ` [PATCH 3/3 v3] Add new tests of ignore-merge-bases Antonio Russo
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=ceeb706d-83ad-c994-121d-d66724d82a49@gmail.com \
--to=antonio.e.russo@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=philipoakley@iee.email \
/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).