From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] rerere-train: modernise a bit
Date: Tue, 15 Feb 2022 23:05:45 -0800 [thread overview]
Message-ID: <xmqqsfsjuw8m.fsf@gitster.g> (raw)
The script wants to create a list of merges using "rev-list" and
filters commits that do not have more than one parent, but if we
always pass "--merges" to "rev-list", there is no need to filter.
The command uses "git show --pretty=format:..." on a single commit
while generating progress reports, which means this title line is
left unterminated. It should have used --pretty=tformat:...
instead, or better yet, use the more modern --format=... to ensure
that the title line is properly terminated.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
contrib/rerere-train.sh | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git c/contrib/rerere-train.sh w/contrib/rerere-train.sh
index 75125d6ae0..499b07e4a6 100755
--- c/contrib/rerere-train.sh
+++ w/contrib/rerere-train.sh
@@ -66,14 +66,9 @@ original_HEAD=$(git rev-parse --verify HEAD) || {
mkdir -p "$GIT_DIR/rr-cache" || exit
-git rev-list --parents "$@" |
+git rev-list --parents --merges "$@" |
while read commit parent1 other_parents
do
- if test -z "$other_parents"
- then
- # Skip non-merges
- continue
- fi
git checkout -q "$parent1^0"
if git merge $other_parents >/dev/null 2>&1
then
@@ -86,7 +81,7 @@ do
fi
if test -s "$GIT_DIR/MERGE_RR"
then
- git show -s --pretty=format:"Learning from %h %s" "$commit"
+ git show -s --format="Learning from %h %s" "$commit"
git rerere
git checkout -q $commit -- .
git rerere
next reply other threads:[~2022-02-16 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 7:05 Junio C Hamano [this message]
2022-02-20 19:52 ` [PATCH] rerere-train: modernise a bit Derrick Stolee
2022-02-27 18:02 ` Johannes Altmanninger
2022-02-27 19:07 ` Re* " Junio C Hamano
2022-02-27 20:23 ` Johannes Altmanninger
2022-02-27 22:13 ` Junio C Hamano
2022-02-27 22:09 ` [PATCH v2] rerere-train: two fixes to the use of "git show -s" Junio C Hamano
2022-02-28 5:33 ` Johannes Altmanninger
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=xmqqsfsjuw8m.fsf@gitster.g \
--to=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.