From: Junio C Hamano <gitster@pobox.com>
To: "Maarten van der Schrieck via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Maarten van der Schrieck <maarten@thingsconnected.nl>
Subject: Re: [PATCH] Documentation: fix statement about rebase.instructionFormat
Date: Wed, 03 Jan 2024 11:22:59 -0800 [thread overview]
Message-ID: <xmqq1qay9q7g.fsf@gitster.g> (raw)
In-Reply-To: <pull.1629.git.git.1704305663254.gitgitgadget@gmail.com> (Maarten van der Schrieck via GitGitGadget's message of "Wed, 03 Jan 2024 18:14:23 +0000")
"Maarten van der Schrieck via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> From: Maarten van der Schrieck <maarten@thingsconnected.nl>
>
> Since commit 62db5247790f2612c0b407a15d1901d88789d35a "rebase -i: generate
> the script via rebase--helper" (Jul 14 2017), the short hash is given in
> rebase-todo. Specifying rebase.instructionFormat does not alter this
> behavior, contrary to what the documentation implies.
>
> Signed-off-by: Maarten van der Schrieck <maarten@thingsconnected.nl>
> ---
Looks good. Will queue. Thanks.
> Documentation: fix statement about rebase.instructionFormat
>
> Since commit 62db5247790f2612c0b407a15d1901d88789d35a "rebase -i:
> generate the script via rebase--helper" (Jul 14 2017), the short hash is
> given in rebase-todo. Specifying rebase.instructionFormat does not alter
> this behavior, contrary to what the documentation implies.
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1629%2Fthingsconnected%2Fpullreq1-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1629/thingsconnected/pullreq1-v1
> Pull-Request: https://github.com/git/git/pull/1629
>
> Documentation/config/rebase.txt | 2 +-
> Documentation/git-rebase.txt | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/config/rebase.txt b/Documentation/config/rebase.txt
> index d59576dbb23..c6187ab28b2 100644
> --- a/Documentation/config/rebase.txt
> +++ b/Documentation/config/rebase.txt
> @@ -40,7 +40,7 @@ rebase.missingCommitsCheck::
> rebase.instructionFormat::
> A format string, as specified in linkgit:git-log[1], to be used for the
> todo list during an interactive rebase. The format will
> - automatically have the long commit hash prepended to the format.
> + automatically have the commit hash prepended to the format.
>
> rebase.abbreviateCommands::
> If set to true, `git rebase` will use abbreviated command names in the
> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
> index 1dd6555f66b..25516c45d8b 100644
> --- a/Documentation/git-rebase.txt
> +++ b/Documentation/git-rebase.txt
> @@ -523,7 +523,7 @@ See also INCOMPATIBLE OPTIONS below.
> +
> The commit list format can be changed by setting the configuration option
> rebase.instructionFormat. A customized instruction format will automatically
> -have the long commit hash prepended to the format.
> +have the commit hash prepended to the format.
> +
> See also INCOMPATIBLE OPTIONS below.
>
>
> base-commit: 055bb6e9969085777b7fab83e3fee0017654f134
prev parent reply other threads:[~2024-01-03 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 18:14 [PATCH] Documentation: fix statement about rebase.instructionFormat Maarten van der Schrieck via GitGitGadget
2024-01-03 19:22 ` Junio C Hamano [this message]
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=xmqq1qay9q7g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=maarten@thingsconnected.nl \
/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).