From: Junio C Hamano <gitster@pobox.com>
To: Jakob Jarmar <jakob.j@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] stash: avoid recursive hard reset on submodules
Date: Fri, 11 Oct 2019 15:02:34 +0900 [thread overview]
Message-ID: <xmqqeezjhlad.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191011001114.GB640501@OJAN-PAAVO.localdomain> (Jakob Jarmar's message of "Fri, 11 Oct 2019 02:11:14 +0200")
Jakob Jarmar <jakob.j@gmail.com> writes:
> git stash push does not recursively stash submodules, but if
> submodule.recurse is set, it may recursively reset --hard them. Having
> only the destructive action recurse is likely to be surprising
> behaviour, and unlikely to be desirable, so the easiest fix should be to
> ensure that the call to git reset --hard never recurses into submodules.
>
> This matches the behavior of check_changes_tracked_files, which ignores
> submodules.
Makes sense. Can we demonstrate an existing breakage and the fix in
a new test or two in perhaps t3906-stash-submodule.sh?
Thanks.
>
> Signed-off-by: Jakob Jarmar <jakob@jarmar.se>
> ---
>
> Sorry for sending a patch with messed up whitespace. This one should be
> correct.
>
> builtin/stash.c | 2 +-
> git-legacy-stash.sh | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/stash.c b/builtin/stash.c
> index b5a301f24d..c986c258f2 100644
> --- a/builtin/stash.c
> +++ b/builtin/stash.c
> @@ -1383,7 +1383,7 @@ static int do_push_stash(const struct pathspec *ps, const char *stash_msg, int q
> struct child_process cp = CHILD_PROCESS_INIT;
> cp.git_cmd = 1;
> argv_array_pushl(&cp.args, "reset", "--hard", "-q",
> - NULL);
> + "--no-recurse-submodules", NULL);
> if (run_command(&cp)) {
> ret = -1;
> goto done;
> diff --git a/git-legacy-stash.sh b/git-legacy-stash.sh
> index f60e9b3e87..07ad4a5459 100755
> --- a/git-legacy-stash.sh
> +++ b/git-legacy-stash.sh
> @@ -370,7 +370,7 @@ push_stash () {
> git diff-index -p --cached --binary HEAD -- "$@" |
> git apply --index -R
> else
> - git reset --hard -q
> + git reset --hard -q --no-recurse-submodules
> fi
>
> if test "$keep_index" = "t" && test -n "$i_tree"
next prev parent reply other threads:[~2019-10-11 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 23:34 [PATCH] stash: avoid recursive hard reset on submodules Jakob Jarmar
2019-10-11 0:11 ` [PATCH v2] " Jakob Jarmar
2019-10-11 6:02 ` Junio C Hamano [this message]
2019-10-11 22:24 ` [PATCH v3] " Jakob Jarmar
2019-10-12 1:46 ` Junio C Hamano
2019-10-12 15:24 ` Jakob Jarmar
2019-10-12 15:38 ` [PATCH v4] " Jakob Jarmar
2019-10-15 1:35 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqeezjhlad.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jakob.j@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).