From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Andy Koppe <andy.koppe@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] pretty: fix lost indent after newline in %w()
Date: Thu, 15 Oct 2026 13:59:39 -0700 [thread overview]
Message-ID: <xmqqwlrillxg.fsf@gitster.g> (raw)
In-Reply-To: <fc0dabfb-3dda-4b12-a1fb-184d1e553623@web.de> ("René Scharfe"'s message of "Thu, 15 Oct 2026 22:42:28 +0200")
René Scharfe <l.s.r@web.de> writes:
> On the other hand this hard newline concept is not explained in the
> docs as far as I can see. That makes it fair game for change in my
> book (within reason), as long as that doc gap is filled. My 2ct..
Yeah, to me, it sounds more productive use of our time and a good
direction.
Thanks.
prev parent reply other threads:[~2026-10-15 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:23 [PATCH] pretty: fix lost indent after newline in %w() Andy Koppe
2026-10-15 20:11 ` Andy Koppe
2026-10-15 20:42 ` René Scharfe
2026-10-15 20:59 ` 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=xmqqwlrillxg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=andy.koppe@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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