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 (Apr 2024, #10; Mon, 29)
Date: Mon, 29 Apr 2024 19:45:49 +0200 [thread overview]
Message-ID: <5209161598ea38138becfdb33e7e8811@manjaro.org> (raw)
In-Reply-To: <xmqqplu8ulra.fsf@gitster.g>
On 2024-04-29 19:22, 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.
>
> Will merge to 'next'?
> source: <cover.1712732383.git.dsimic@manjaro.org>
Oh, nice, this is reassuring... I'd be so happy to see those patches
accepted, which would avoid wasting all the effort that went into them,
while also making "git send-email" a bit more user friendly. :)
next prev parent reply other threads:[~2024-04-29 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 17:22 What's cooking in git.git (Apr 2024, #10; Mon, 29) Junio C Hamano
2024-04-29 17:45 ` Dragan Simic [this message]
2024-04-29 18:05 ` Patrick Steinhardt
2024-04-30 4:45 ` Linus Arver
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=5209161598ea38138becfdb33e7e8811@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).