git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Zhang Yi <18994118902@163.com>
Cc: git@vger.kernel.org, v.garg.work@gmail.com
Subject: Re: [GSOC] [PATCH v2 0/3] t9700:moderizen test scripts
Date: Thu, 23 Feb 2023 18:49:04 -0800	[thread overview]
Message-ID: <xmqqo7pj3hi7.fsf@gitster.g> (raw)
In-Reply-To: 20230224013413.1969003-1-18994118902@163.com

Zhang Yi <18994118902@163.com> writes:

> The style of t9700-perl-git.sh is old.There are 3 things need improve:
> * A title is not on the same line with test_expect_success command.Need to combine them.
> * A test body is indented by whitespaces.Need to replace whitespaces by TAB
> * There are whitespaces after redirect operators.Need to delete whitespaces.
>
> ---
> Thanks for all suggestions.Here are so many interesting things to learn.

It is a good idea to summarize the difference between the previous
round and this round, to help reviewers who have already spent
cycles to review the previous round to skim the parts of the updated
series that haven't been changed (and they have already reviewed).

And the cover letter is the ideal place to do so.

Alternatively, you can write after the three-dash lines between the
proposed log message and the patch text of each patch message.

> Zhang Yi (3):
>   t9700:fix title style
>   t9700:change indents to TAB
>   t9700:delete whitespaces after redirect operators

You are missing space after the colon, all of them.  Also you are
missing space after full-stop that concludes each sentence in all of
your proposed log messages.

Even though you _could_ treat these three things as logically
separate changes, I would suspect that each of them is so small that
it may be easier to review as a single patch.

Thanks.

  parent reply	other threads:[~2023-02-24  2:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  4:07 [GSOC] [PATCH v1 0/2] Modernize t9700 test script Zhang Yi
2023-02-22  4:07 ` [GSOC] [PATCH v1 1/2] Fix title style Zhang Yi
2023-02-22  7:13   ` Vivan Garg
2023-02-22  4:07 ` [GSOC] [PATCH v1 2/2] Change indents to TAB Zhang Yi
2023-02-22  7:24   ` Vivan Garg
2023-02-22  7:09 ` [GSOC] [PATCH v1 0/2] Modernize t9700 test script Vivan Garg
2023-02-24  1:34   ` [GSOC] [PATCH v2 0/3] t9700:moderizen test scripts Zhang Yi
2023-02-24  1:34     ` [GSOC] [PATCH v2 1/3] t9700:fix title style Zhang Yi
2023-02-24  1:34     ` [GSOC] [PATCH v2 2/3] t9700:change indents to TAB Zhang Yi
2023-02-24  1:34     ` [GSOC] [PATCH v2 3/3] t9700:delete whitespaces after redirect operators Zhang Yi
2023-02-24 11:20       ` Philip Oakley
2023-02-24  2:49     ` Junio C Hamano [this message]
2023-02-24  3:31       ` Re:Re: [GSOC] [PATCH v2 0/3] t9700:moderizen test scripts Zhang Yi
2023-02-25  1:30   ` [GSOC] [PATCH v3 1/1] t9700: modernize " Zhang Yi

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=xmqqo7pj3hi7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=18994118902@163.com \
    --cc=git@vger.kernel.org \
    --cc=v.garg.work@gmail.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).