git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2024, #02; Fri, 3)
Date: Sat, 04 May 2024 04:59:19 +0200	[thread overview]
Message-ID: <a07d3807a24f6d68cb48ee48366ae25e@manjaro.org> (raw)
In-Reply-To: <xmqqa5l64e0i.fsf@gitster.g>

On 2024-05-04 02:27, Junio C Hamano wrote:
> * ds/send-email-per-message-block (2024-04-10) 2 commits
>  - send-email: make it easy to discern the messages for each patch
>  - send-email: move newline characters out of a few translatable 
> strings
> 
>  "git send-email" learned to separate its reports on each message it
>  sends out with an extra blank line in between.
> 
>  Comments?
>  source: <cover.1712732383.git.dsimic@manjaro.org>

After thinking a bit more about these patches, I think that the second
patch in the series ("send-email: make it easy to discern the messages
for each patch") should be dropped, but the first patch ("send-email:
move newline characters out of a few translatable strings") should have
no roadblocks that prevent it from becoming applied to "next".

The reason why I'm proposing that the second patch gets dropped is that
I now think there are better ways to utilize the vertical screen space
in the outputs produced by "git send-email".  I'll keep thinking about
it for a while, and possibly submit a clean and irresistible [1] patch
at some point in the future.

[1] 
https://lore.kernel.org/git/72c114086590b9b15a3fdd9e0d6bd67e@manjaro.org/


  reply	other threads:[~2024-05-04  2:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04  0:27 What's cooking in git.git (May 2024, #02; Fri, 3) Junio C Hamano
2024-05-04  2:59 ` Dragan Simic [this message]
2024-05-04  8:58 ` ds/scalar-reconfigure-all-fix, was " Johannes Schindelin
2024-05-06  9:21 ` Patrick Steinhardt
2024-05-06 22:17   ` Junio C Hamano
2024-05-07  6:05     ` Junio C Hamano
2024-05-07  6:15       ` Patrick Steinhardt

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a07d3807a24f6d68cb48ee48366ae25e@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).