From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/1] merge/pull: extend merge.stat configuration variable to cover --compact-summary
Date: Wed, 11 Jun 2025 10:29:19 -0700 [thread overview]
Message-ID: <xmqq7c1ii3v4.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cRgUWYGPb7o_9UgeQAuE5WN1mtC=bsOP=62rXOzjXJ5Eg@mail.gmail.com> (Eric Sunshine's message of "Wed, 11 Jun 2025 13:12:20 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> Do we want \EOF (with backslash)?
>
>> + Updating FROM..TO
>> + Fast-forward
>> + file | 2 +-
>> + other (new) | 9 +++++++++
>> + 2 files changed, 10 insertions(+), 1 deletion(-)
>> + EOF
Indeed. There is no interpolation necessary for the contents, so it
is a very good idea to do that. The same for the test part of
[1/1].
Thanks.
prev parent reply other threads:[~2025-06-11 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 16:05 [PATCH] merge/pull: --compact-summary Junio C Hamano
2025-06-10 21:16 ` D. Ben Knoble
2025-06-11 3:12 ` Junio C Hamano
2025-06-11 23:26 ` D. Ben Knoble
2025-06-11 17:00 ` [PATCH 2/1] merge/pull: extend merge.stat configuration variable to cover --compact-summary Junio C Hamano
2025-06-11 17:12 ` Eric Sunshine
2025-06-11 17:29 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7c1ii3v4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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.
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 NNTP newsgroup(s).