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

Re: [PATCH 0/1] worktree: teach "add" to ignore submodule.recurse config

From
PBPhilippe Blain <philippe.blain@me.com>
Date
Oct 29, 2019, 12:33 UTC
Message-ID
<85CAC41A-A0EA-4E22-BC22-F57A59D76678@me.com>
In-Reply-To
<xmqqtv7ta9lz.fsf@gitster-ct.c.googlers.com>
Hi Junio,

That indeed makes the trick. Thanks! Should I send a separate patch series with this patch ? How would that work ? "Signed-off by" me and "Based-on-patch-by" you ?

Philippe.
Show 28 quoted lines
> Le 27 oct. 2019 à 22:26, Junio C Hamano <gitster@pobox.com> a écrit :
> 
> I am not sure if the compiler needs fixing in this case, but the
> following may work it around.
> 
> builtin/merge.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/builtin/merge.c b/builtin/merge.c
> index e2ccbc44e2..0746f11df2 100644
> --- a/builtin/merge.c
> +++ b/builtin/merge.c
> @@ -826,9 +826,12 @@ static void prepare_to_commit(struct commit_list *remoteheads)
> 			strbuf_commented_addf(&msg, "\n");
> 		}
> 		strbuf_commented_addf(&msg, _(merge_editor_comment));
> -		strbuf_commented_addf(&msg, _(cleanup_mode == COMMIT_MSG_CLEANUP_SCISSORS ?
> -			scissors_editor_comment :
> -			no_scissors_editor_comment), comment_line_char);
> +
> +		if (cleanup_mode == COMMIT_MSG_CLEANUP_SCISSORS)
> +			strbuf_commented_addf(&msg, _(scissors_editor_comment));
> +		else
> +			strbuf_commented_addf(&msg, _(no_scissors_editor_comment),
> +					      comment_line_char);
> 	}
> 	if (signoff)
> 		append_signoff(&msg, ignore_non_trailer(msg.buf, msg.len), 0);
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 5 in “worktree: teach "add" to ignore submodule.recurse config”
  1. 0/1 worktree: teach "add" to ignore submodule.recurse configPhilippe Blain via GitGitGadget, Oct 27, 2019
  2. 1/1 worktree: teach "add" to ignore submodule.recurse configPhilippe Blain via GitGitGadget, Oct 27, 2019
  3. Junio C HamanoOct 28, 2019
  4. Philippe BlainOct 29, 2019
  5. Junio C HamanoOct 30, 2019

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.