git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Kristoffer Haugsbakk <code@khaugsbakk.name>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] send-email: make it easy to discern the messages for each patch
Date: Fri, 05 Apr 2024 09:07:32 +0200	[thread overview]
Message-ID: <37827a9d31e494074310024b86b242c0@manjaro.org> (raw)
In-Reply-To: <70c97d51-b26a-43f3-9856-af405f396576@app.fastmail.com>

Hello Kristoffer,

On 2024-04-05 08:52, Kristoffer Haugsbakk wrote:
> On Thu, Apr 4, 2024, at 22:34, Dragan Simic wrote:
>> may be seen as redundant.  Though, it doesn't look too bad, and making 
>> that
>> last newline not displayed would make the code much more complex, 
>> which would
>> not be worth neither the time and effort now, nor the additional 
>> maintenance
>> burden in the future.
> 
> “Not worth neither” looks like a double negative. A double negative in
> mainstream English leads to cancellation, unlike in some regional
> dialects where it acts as an intensifier of sorts.

Good point! :)  However, that part of the patch description has already
been deleted for the future v3 of this patch, because it treats the 
vertical
whitespace as separators, instead of as terminators.


      reply	other threads:[~2024-04-05  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 20:34 [PATCH v2] send-email: make it easy to discern the messages for each patch Dragan Simic
2024-04-04 22:52 ` Junio C Hamano
2024-04-04 23:44   ` Dragan Simic
2024-04-05 16:44     ` Junio C Hamano
2024-04-05 16:51       ` Dragan Simic
2024-04-05 17:13         ` Junio C Hamano
2024-04-05 17:18           ` Dragan Simic
2024-04-05  6:52 ` Kristoffer Haugsbakk
2024-04-05  7:07   ` Dragan Simic [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

  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=37827a9d31e494074310024b86b242c0@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=code@khaugsbakk.name \
    --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).