From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Patryk Obara <patryk.obara@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] t750*: make tests for commit messages more pedantic
Date: Thu, 28 May 2015 11:55:53 -0700 [thread overview]
Message-ID: <xmqqh9qwh6py.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPig+cRHB3Qzm-e1_KROu2RQoW2rftLH=uKrWQBsnW0EYkcLPw@mail.gmail.com> (Eric Sunshine's message of "Thu, 28 May 2015 09:34:14 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Tue, May 26, 2015 at 2:15 AM, Patryk Obara <patryk.obara@gmail.com> wrote:
>> Currently messages are compared with --pretty=format:%s%b which does
>> not retain raw format of commit message. In result it's not clear what
>> part of expected commit msg is subject and what part is body. Also, it's
>> impossible to test if messages with multiple lines are handled
>> correctly, which may be significant when using nondefault --cleanup.
>
> Makes sense.
> ...
>> +test_expect_success 'template without newline before eof should work with --status' '
>
> It's not clear what "should work" means. I suppose you mean that the
> end result should have exactly one newline after the template. Perhaps
> the test title could indicate the intent more clearly.
I agree that what "should work" in this title is unclear.
Because there is nothing wrong in the current system, if a follow-up
patch plans to change the established behaviour, the tests in this
"currently we do not test blank lines, so add tests for them" patch
should limit themselves to document the current behaviour.
Then a follow-up patch that modifies the behaviour can show how the
updated behaviour is different and illustrate in what way it is
better than the current behaviour. That would be one way to justify
the change.
next prev parent reply other threads:[~2015-05-28 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 6:15 [PATCH 0/2] commit -t appends newline after template file Patryk Obara
2015-05-26 6:15 ` [PATCH 1/2] t750*: make tests for commit messages more pedantic Patryk Obara
2015-05-28 13:34 ` Eric Sunshine
2015-05-28 18:55 ` Junio C Hamano [this message]
2015-05-26 6:15 ` [PATCH 2/2] commit: fix ending newline for template files Patryk Obara
2015-05-28 14:29 ` Eric Sunshine
2015-05-28 18:22 ` Junio C Hamano
2015-05-28 18:35 ` Eric Sunshine
2015-05-29 20:17 ` Junio C Hamano
2015-05-29 22:25 ` Eric Sunshine
2015-05-30 11:29 ` Patryk Obara
2015-05-31 2:21 ` Eric Sunshine
2015-05-30 16:59 ` Junio C Hamano
2015-05-28 10:06 ` [PATCH 0/2] commit -t appends newline after template file Patryk Obara
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=xmqqh9qwh6py.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=patryk.obara@gmail.com \
--cc=sunshine@sunshineco.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.