git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] subtree: force merge commit

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 18, 2021, 04:53 UTC
Message-ID
<xmqqpmqy12u0.fsf@gitster.g>
In-Reply-To
<pull.1139.v2.git.git.1636926322423.gitgitgadget@gmail.com>
"Thomas Koutcher via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 9 quoted lines
> From: Thomas Koutcher <thomas.koutcher@online.fr>
>
> When `merge.ff` is set to `only` in .gitconfig, `git subtree pull` will
> fail with error `fatal: Not possible to fast-forward, aborting.`, but
> the command does want to make merges in these places. Add `--no-ff`
> argument to `git merge` to enforce this behaviour.
>
> Reviewed-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> Reviewed-by: Junio C Hamano <gitster@pobox.com>
Reviewed-by: is a bit tricky.  If you are sending a corrected
version after other people just took a look at a previous iteration,
you cannot generally have them for two reasons.  First of all, they
haven't said that you can have Reviewed-by: under there name (which
means that they are completely satisfied after giving a thorough
analysis).  Also, the version you are sending is different from what
they reviewed, so even if they were happy with the previous iteration,
it does not mean they would be with this version.
Show 16 quoted lines
> diff --git a/contrib/subtree/git-subtree.sh b/contrib/subtree/git-subtree.sh
> index 7f767b5c38f..cb51aee4cbf 100755
> --- a/contrib/subtree/git-subtree.sh
> +++ b/contrib/subtree/git-subtree.sh
> @@ -976,10 +976,10 @@ cmd_merge () {
>  
>  	if test -n "$arg_addmerge_message"
>  	then
> -		git merge -Xsubtree="$arg_prefix" \
> +		git merge --no-ff -Xsubtree="$arg_prefix" \
>  			--message="$arg_addmerge_message" "$rev"
>  	else
> -		git merge -Xsubtree="$arg_prefix" $rev
> +		git merge --no-ff -Xsubtree="$arg_prefix" $rev
>  	fi
>  }
Thanks.  I'll drop these two reviewed-by lines while queuing.
Previous: Thomas Koutcher via GitGitGadgetNext: Thomas Koutcher
Message 5 of 10 in “subtree: ignore merge.ff setting”
  1. subtree: ignore merge.ff settingThomas Koutcher via GitGitGadget, Nov 14, 2021
  2. Ævar Arnfjörð BjarmasonNov 14, 2021
  3. Junio C HamanoNov 14, 2021
  4. subtree: force merge commitThomas Koutcher via GitGitGadget, Nov 14, 2021
  5. Junio C HamanoNov 18, 2021
  6. Thomas KoutcherNov 18, 2021
  7. subtree: force merge commitJohannes Altmanninger, Feb 1, 2022
  8. Junio C HamanoFeb 1, 2022
  9. Johannes AltmanningerFeb 1, 2022
  10. Junio C HamanoFeb 1, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.