From: "James Limbouris via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
James Limbouris <james@digitalmatter.com>,
James Limbouris <james@digitalmatter.com>
Subject: [PATCH v4] subtree: fix argument handling in check_parents
Date: Wed, 08 Dec 2021 02:11:58 +0000 [thread overview]
Message-ID: <pull.1086.v4.git.1638929518657.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1086.v3.git.1638758742741.gitgitgadget@gmail.com>
From: James Limbouris <james@digitalmatter.com>
315a84f9aa0 (subtree: use commits before rejoins for splits, 2018-09-28)
changed the signature of check_parents from 'check_parents [REV...]'
to 'check_parents PARENTS_EXPR INDENT'. In other words the variable list
of parent revisions became a list embedded in a string. However it
neglected to unpack the list again before sending it to cache_miss,
leading to incorrect calls whenever more than one parent was present.
This is the case whenever a merge commit is processed, with the end
result being a loss of performance from unecessary rechecks.
The indent parameter was subsequently removed in e9525a8a029 (subtree:
have $indent actually affect indentation, 2021-04-27), but the argument
handling bug remained.
For consistency, take multiple arguments in check_parents,
and pass all of them to cache_miss separately.
Signed-off-by: James Limbouris <james@digitalmatter.com>
---
subtree: fix argument handling in check_parents
> I saw that you sent a v3, but did not see any of this information
> (which took a good while to assemble, as you might have guessed) in
> the commit message. However, I think that message would make for the
> best home for this information.
Sorry Dscho - it wasn't 100% clear to me which details were required.
I've rerolled and tried again. Also sorry if I'm not replying to the
mail correctly - I'm not actually subscribed to the list, and this seems
like the only easy way to get text onto it through gitgitgadget without
fighting Outlook.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1086%2Fjamesl-dm%2Fmaint-v4
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1086/jamesl-dm/maint-v4
Pull-Request: https://github.com/gitgitgadget/git/pull/1086
Range-diff vs v3:
1: f734ca9d276 ! 1: cdc5295a7ac subtree: fix argument handling in check_parents
@@ Metadata
## Commit message ##
subtree: fix argument handling in check_parents
- check_parents was taking all of its arguments as a single string,
- and erroneously passing them to cache_miss as a single string. For
- commits with a single parent this would succeed, but whenever a merge
- commit was processed, cache_miss would be passed "parent1 parent2"
- instead of "parent1" "parent2" and fail, leading to unecessary rechecks
- of the parent commits.
+ 315a84f9aa0 (subtree: use commits before rejoins for splits, 2018-09-28)
+ changed the signature of check_parents from 'check_parents [REV...]'
+ to 'check_parents PARENTS_EXPR INDENT'. In other words the variable list
+ of parent revisions became a list embedded in a string. However it
+ neglected to unpack the list again before sending it to cache_miss,
+ leading to incorrect calls whenever more than one parent was present.
+ This is the case whenever a merge commit is processed, with the end
+ result being a loss of performance from unecessary rechecks.
+
+ The indent parameter was subsequently removed in e9525a8a029 (subtree:
+ have $indent actually affect indentation, 2021-04-27), but the argument
+ handling bug remained.
For consistency, take multiple arguments in check_parents,
and pass all of them to cache_miss separately.
contrib/subtree/git-subtree.sh | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/contrib/subtree/git-subtree.sh b/contrib/subtree/git-subtree.sh
index 7f767b5c38f..71f1fd94bde 100755
--- a/contrib/subtree/git-subtree.sh
+++ b/contrib/subtree/git-subtree.sh
@@ -296,10 +296,9 @@ cache_miss () {
done
}
-# Usage: check_parents PARENTS_EXPR
+# Usage: check_parents [REVS...]
check_parents () {
- assert test $# = 1
- missed=$(cache_miss "$1") || exit $?
+ missed=$(cache_miss "$@") || exit $?
local indent=$(($indent + 1))
for miss in $missed
do
@@ -753,7 +752,7 @@ process_split_commit () {
fi
createcount=$(($createcount + 1))
debug "parents: $parents"
- check_parents "$parents"
+ check_parents $parents
newparents=$(cache_get $parents) || exit $?
debug "newparents: $newparents"
base-commit: e9d7761bb94f20acc98824275e317fa82436c25d
--
gitgitgadget
next prev parent reply other threads:[~2021-12-08 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 2:06 [PATCH] subtree: fix argument handling in check_parents James Limbouris via GitGitGadget
2021-12-01 23:04 ` Junio C Hamano
2021-12-02 5:51 ` [PATCH v2] " James Limbouris via GitGitGadget
2021-12-06 2:45 ` [PATCH v3] " James Limbouris via GitGitGadget
2021-12-08 2:11 ` James Limbouris via GitGitGadget [this message]
2022-01-04 12:21 ` [PATCH v4] " Johannes Schindelin
2022-01-04 20:04 ` Junio C Hamano
2021-12-03 15:22 ` [PATCH] " Johannes Schindelin
2021-12-03 20:02 ` Junio C Hamano
2021-12-07 21:45 ` Johannes Schindelin
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=pull.1086.v4.git.1638929518657.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=james@digitalmatter.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 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.