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: [PATCH v2] send-email: make it easy to discern the messages for each patch
Date: Fri, 05 Apr 2024 18:51:55 +0200	[thread overview]
Message-ID: <fa91b134e6cb18578d9c499f584ae3c5@manjaro.org> (raw)
In-Reply-To: <xmqqjzlbwyhr.fsf@gitster.g>

Hello Junio,

On 2024-04-05 18:44, Junio C Hamano wrote:
> Dragan Simic <dsimic@manjaro.org> writes:
> 
>> Well, I actually wasn't lazy, but instead I wanted to give this patch
>> better chances to be accepted, by introducing as a small amount of
>> changes to the code as possible.  This was a lesson not to take that
>> route, but to do "the right thing" instead.
> 
> The lesson you should be taking is a bit different here, though.
> 
> As we discussed, doing the separator correctly is harder and doing
> the terminator correctly is much easier and less error prone.  So if
> we chose to do terminator semantics and punt on doing separator
> semantics, the right thing could have been to adjust the existing
> tests to make sure that the new output with unnecessary trailing
> blank line is expected.
> 
> Either that, or we should fix the code not to break the current
> expectation.  Doing neither of these is not quite acceptable---
> that is the lesson from this episode, I would think.

Of course, it was my mistake not to either ensure that the tests
still pass after the introduced changes, or to adjust the test(s)
accordingly.

However, making the vertical whitespace a separator also follows
the Git's general approach of not wasting the vertical screen
space whenever possible, so taking the separator route is actually
better, if you agree.


  reply	other threads:[~2024-04-05 16:52 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 [this message]
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

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=fa91b134e6cb18578d9c499f584ae3c5@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).