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

Re: [PATCH] rebase-am: fix regression with new cover-letter config

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 15, 2013, 01:48 UTC
Message-ID
<7vhaj84l8m.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1365978424-11841-1-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 9 quoted lines
> If you have a cover-letter configuration set to anything other than
> 'false', 'git format-patch' might generate a cover letter, and 'git am'
> doesn't seem to like that.
>
> Ideally 'git am' should skip the cover-letter, but for now lets just fix
> the regression.
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
This is a follow-up to the fc/send-email-annotate topic, right?

You are mean to say "fix regression", which gave me a small heart attack ;-). I was worried if we had already merged it to 'next'.

As I already wrote in the recent "What's cooking", the series looks good to me. I am inclined to say that we should merge it (together with this update) to 'next'.

Thanks for catching this before breaking the real world users.
Show 18 quoted lines
>  git-rebase--am.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/git-rebase--am.sh b/git-rebase--am.sh
> index 97f31dc..f84854f 100644
> --- a/git-rebase--am.sh
> +++ b/git-rebase--am.sh
> @@ -31,8 +31,8 @@ else
>  	rm -f "$GIT_DIR/rebased-patches"
>  
>  	git format-patch -k --stdout --full-index --ignore-if-in-upstream \
> -		--src-prefix=a/ --dst-prefix=b/ \
> -		--no-renames $root_flag "$revisions" >"$GIT_DIR/rebased-patches"
> +		--src-prefix=a/ --dst-prefix=b/ --no-renames --no-cover-letter \
> +		$root_flag "$revisions" >"$GIT_DIR/rebased-patches"
>  	ret=$?
>  
>  	if test 0 != $ret
Previous: Felipe ContrerasNext: Felipe Contreras
Message 2 of 5 in “rebase-am: fix regression with new cover-letter config”
  1. rebase-am: fix regression with new cover-letter configFelipe Contreras, Apr 14, 2013
  2. Junio C HamanoApr 15, 2013
  3. Felipe ContrerasApr 15, 2013
  4. Junio C HamanoApr 15, 2013
  5. Eric SunshineApr 15, 2013

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.