From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> To: git@vger.kernel.org Cc: Jonathan Tan <jonathantanmy@google.com>, Stefan Beller <stefanbeller@gmail.com>, Brandon Williams <bwilliamseng@gmail.com>, Brice Goglin <bgoglin@free.fr>, Philippe Blain <levraiphilippeblain@gmail.com> Subject: [PATCH 0/4] Fix 'pull --rebase --recurse-submodules' when local and upstream branches have no fork-point Date: Sat, 14 Nov 2020 00:34:41 +0000 [thread overview] Message-ID: <pull.789.git.1605314085.gitgitgadget@gmail.com> (raw) This series fixes a bug in 'git pull --rebase --recurse-submodules' when the current branch and the remote-tracking branch we are pulling from have no fork-point (git merge-base --fork-point refs/remotes/<remote>/<upstream> <current-branch> returns empty), resulting in a misleading and fatal error message: fatal: cannot rebase with locally recorded submodule modifications This is patch 4/4. Patch 1/4 is a preparatory refactoring, and patches 2-3 add comments to t5552-pull-submodules to describe 'pull --rebase --recurse-submodules' tests a little better. Philippe Blain (4): pull --rebase: compute rebase arguments in separate function t5572: add notes on a peculiar test t5572: describe '--rebase' tests a little more pull: check for local submodule modifications with the right range builtin/pull.c | 48 ++++++++++++++++++++++++--------- t/t5572-pull-submodule.sh | 56 +++++++++++++++++++++++++++++++++++++-- 2 files changed, 90 insertions(+), 14 deletions(-) base-commit: e4d83eee9239207622e2b1cc43967da5051c189c Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-789%2Fphil-blain%2Fpull-recurse-no-fork-point-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-789/phil-blain/pull-recurse-no-fork-point-v1 Pull-Request: https://github.com/gitgitgadget/git/pull/789 -- gitgitgadget
next reply other threads:[~2020-11-14 0:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-14 0:34 Philippe Blain via GitGitGadget [this message] 2020-11-14 0:34 ` [PATCH 1/4] pull --rebase: compute rebase arguments in separate function Philippe Blain via GitGitGadget 2020-11-14 0:34 ` [PATCH 2/4] t5572: add notes on a peculiar test Philippe Blain via GitGitGadget 2020-11-14 0:34 ` [PATCH 3/4] t5572: describe '--rebase' tests a little more Philippe Blain via GitGitGadget 2020-11-14 0:34 ` [PATCH 4/4] pull: check for local submodule modifications with the right range Philippe Blain via GitGitGadget
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=pull.789.git.1605314085.gitgitgadget@gmail.com \ --to=gitgitgadget@gmail.com \ --cc=bgoglin@free.fr \ --cc=bwilliamseng@gmail.com \ --cc=git@vger.kernel.org \ --cc=jonathantanmy@google.com \ --cc=levraiphilippeblain@gmail.com \ --cc=stefanbeller@gmail.com \ --subject='Re: [PATCH 0/4] Fix '\''pull --rebase --recurse-submodules'\'' when local and upstream branches have no fork-point' \ /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
Code repositories for project(s) associated with this 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).