From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, Kim Gybels <kgybels@infogroep.be>,
"Matwey V. Kornilov" <matwey.kornilov@gmail.com>
Subject: Re: [PATCH] rebase -p: fix quoting when calling `git merge`
Date: Fri, 05 Jan 2018 12:30:18 -0800 [thread overview]
Message-ID: <xmqqvaggaw11.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <8cafe900ce97d885c58f4a7f02e748d2ae3b02a2.1515101305.git.johannes.schindelin@gmx.de> (Johannes Schindelin's message of "Thu, 4 Jan 2018 22:31:52 +0100 (STD)")
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> git-rebase--interactive.sh | 9 ++++++---
> t/t3418-rebase-continue.sh | 14 ++++++++++++++
> 2 files changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index e3f5a0abf3c..085aa068cbb 100644
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -392,9 +392,12 @@ pick_one_preserving_merges () {
> new_parents=${new_parents# $first_parent}
> merge_args="--no-log --no-ff"
> if ! do_with_author output eval \
> - 'git merge ${gpg_sign_opt:+"$gpg_sign_opt"} \
> - $allow_rerere_autoupdate $merge_args \
> - $strategy_args -m "$msg_content" $new_parents'
> + git merge ${gpg_sign_opt:+$(git rev-parse \
> + --sq-quote "$gpg_sign_opt")} \
> + $allow_rerere_autoupdate "$merge_args" \
> + "$strategy_args" \
> + -m $(git rev-parse --sq-quote "$msg_content") \
> + "$new_parents"
Makes sense. I should have been more careful when reviewing
db2b3b820e2.
Thanks.
next prev parent reply other threads:[~2018-01-05 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 21:31 [PATCH] rebase -p: fix quoting when calling `git merge` Johannes Schindelin
2018-01-05 20:30 ` Junio C Hamano [this message]
2018-01-05 21:14 ` 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=xmqqvaggaw11.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=kgybels@infogroep.be \
--cc=matwey.kornilov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox