doc: add missing commit C to the graph for --ancestry-path=H D..M

[jhcarl0814]

cc:Elijah Newren [email protected],D. Ben Knoble [email protected]

[gitgitgadget]

Welcome to GitGitGadget

Hi @jhcarl0814, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests.

Please make sure that either:

• Your Pull Request has a good description, if it consists of multiple commits, as it will be used as cover letter.
• Your Pull Request description is empty, if it consists of a single commit, as the commit message should be descriptive enough by itself.

You can CC potential reviewers by adding a footer to the PR description with the following syntax:

CC: Revi Ewer <[email protected]>, Ill Takalook <[email protected]>

NOTE: DO NOT copy/paste your CC list from a previous GGG PR's description,
because it will result in a malformed CC list on the mailing list. See
example.

Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:

• the lines should not exceed 76 columns,
• the first line should be like a header and typically start with a prefix like "tests:" or "revisions:" to state which subsystem the change is about, and
• the commit messages' body should be describing the "why?" of the change.
• Finally, the commit messages should end in a Signed-off-by: line matching the commits' author.

It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code.

Contributing the patches

Before you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form /allow. A good way to find other contributors is to locate recent pull requests where someone has been /allowed:

• Search: is:pr is:open "/allow"

Both the person who commented /allow and the PR author are able to /allow you.

An alternative is the channel #git-devel on the Libera Chat IRC network:

<newcontributor> I've just created my first PR, could someone please /allow me? https://github.com/gitgitgadget/git/pull/12345
<veteran> newcontributor: it is done
<newcontributor> thanks!

Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment /submit.

If you want to see what email(s) would be sent for a /submit request, add a PR comment /preview to have the email(s) sent to you. You must have a public GitHub email address for this. Note that any reviewers CC'd via the list in the PR description will not actually be sent emails.

After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail).

If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the (raw) link), then import it into your mail program. If you use GMail, you can do this via:

curl -g --user "<EMailAddress>:<Password>" \
    --url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt

To iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description):

Changes since v1:
- Fixed a typo in the commit message (found by ...)
- Added a code comment to ... as suggested by ...
...

To send a new iteration, just add another PR comment with the contents: /submit.

Need help?

New contributors who want advice are encouraged to join [email protected], where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join.

You may also be able to find help in real time in the developer IRC channel, #git-devel on Libera Chat. Remember that IRC does not support offline messaging, so if you send someone a private message and log out, they cannot respond to you. The scrollback of #git-devel is archived, though.

[jhcarl0814]

/submit

[gitgitgadget]

Error: User jhcarl0814 is not yet permitted to use GitGitGadget

[Unique-Usman]

/allow

[gitgitgadget]

User jhcarl0814 is now allowed to use GitGitGadget.

[jhcarl0814]

@Unique-Usman Thanks!

[jhcarl0814]

/submit

[gitgitgadget]

Submitted as [email protected]

To fetch this version into FETCH_HEAD:

git fetch https://github.com/gitgitgadget/git/ pr-1883/jhcarl0814/patch_ancestry_path_doc_graph_20250315-v1

To fetch this version to local tag pr-1883/jhcarl0814/patch_ancestry_path_doc_graph_20250315-v1:

git fetch --no-tags https://github.com/gitgitgadget/git/ tag pr-1883/jhcarl0814/patch_ancestry_path_doc_graph_20250315-v1

[gitgitgadget]

On the Git mailing list, Elijah Newren wrote (reply to this):

On Sat, Mar 15, 2025 at 6:47 PM Han Jiang via GitGitGadget
<[email protected]> wrote:
>
> From: Han Jiang <[email protected]>
>
> The graph for `--ancestry-path=H D..M` should contain commit C.

Yep, C is in the range D..M and C is also an ancestor of H.

> Signed-off-by: Han Jiang <[email protected]>
> ---
>     doc: add missing commit C to the graph for --ancestry-path=H D..M
>
>     cc:Elijah Newren [email protected],D. Ben Knoble [email protected]

In the future, you'll probably want to use separate cc lines for each
person you are cc'ing; I think gitgitgadget expects that to work.  You
also might want to add a space after the "cc:", though I don't know if
that's required.

> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1883%2Fjhcarl0814%2Fpatch_ancestry_path_doc_graph_20250315-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1883/jhcarl0814/patch_ancestry_path_doc_graph_20250315-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/1883
>
>  Documentation/rev-list-options.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/rev-list-options.adoc b/Documentation/rev-list-options.adoc
> index 785c0786e0c..5e5cedb9127 100644
> --- a/Documentation/rev-list-options.adoc
> +++ b/Documentation/rev-list-options.adoc
> @@ -640,7 +640,7 @@ commits affected by that topic, we may only want to view the subset of
>  -----------------------------------------------------------------------
>                 E
>                  \
> -                 G---H---I---J
> +             C---G---H---I---J
>                                \
>                                 L--M
>  -----------------------------------------------------------------------
>
> base-commit: 683c54c999c301c2cd6f715c411407c413b1d84e
> --
> gitgitgadget

Patch looks good.

[gitgitgadget]

On the Git mailing list, Han Jiang wrote (reply to this):

On Sun, Mar 16, 2025 at 7:53 PM Elijah Newren <[email protected]> wrote:
>
> In the future, you'll probably want to use separate cc lines for each
> person you are cc'ing; I think gitgitgadget expects that to work.  You
> also might want to add a space after the "cc:", though I don't know if
> that's required.

Thank you for your suggestion! I will follow it next time.

[gitgitgadget]

This patch series was integrated into seen via git@30afefa.

[gitgitgadget]

This patch series was integrated into seen via git@ad45fb4.

[gitgitgadget]

This patch series was integrated into next via git@e94155a.

[gitgitgadget]

This patch series was integrated into seen via git@edc7515.

[gitgitgadget]

This branch is now known as hj/doc-rev-list-ancestry-fix.

[gitgitgadget]

This patch series was integrated into seen via git@70ce12f.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch hj/doc-rev-list-ancestry-fix on the Git mailing list:

Doc update.

Will merge to 'master'.
source: <[email protected]>

[gitgitgadget]

This patch series was integrated into seen via git@9b33eca.

[gitgitgadget]

This patch series was integrated into seen via git@b1a4120.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch hj/doc-rev-list-ancestry-fix on the Git mailing list:

Doc update.

Will merge to 'master'.
source: <[email protected]>

[gitgitgadget]

This patch series was integrated into seen via git@2948e61.

[gitgitgadget]

This patch series was integrated into seen via git@30eadc9.

[gitgitgadget]

This patch series was integrated into master via git@30eadc9.

[gitgitgadget]

This patch series was integrated into next via git@30eadc9.

[gitgitgadget]

Closed via 30eadc9.