git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AbdAlRahman Gad <abdobngad@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v6 0/8] [Newcomer] t7004: modernize the style
Date: Wed, 14 Aug 2024 00:58:44 +0300	[thread overview]
Message-ID: <9a51779c-5404-40af-9e44-dfa05785c569@gmail.com> (raw)
In-Reply-To: <CAPig+cSLzNyik6x2FQo6T4fAtTAsH07=y3g=MTXcSTvR7S2Vqg@mail.gmail.com>



On 8/13/24 10:57 PM, Eric Sunshine wrote:
> On Thu, Aug 8, 2024 at 12:34 PM AbdAlRahman Gad <abdobngad@gmail.com> wrote:
>> - Remove whitespace after the redirect operators.
>>
>> - Move number of expect files prepared outside of
>>    test_expect_success to be inside the tests that use it.
>> [...]
>> There are still tests that could lose exit status to pipe. This needs
>> to be modernized too, I will fix them in another patch series.
> 
> Thanks. This sort of information -- explaining the aim of the series
> and explaining what will be done later -- is appreciated by reviewers.
> 
> There are a few additional pieces of information you can include in
> the cover letter to make life even simpler for reviewers:
> 
> * provide a link to the previous version of the series
> 
> * explain what differs in this version as compared with the previous version
> 
> * include a range-diff showing the actual changes between this version
> and the previous version (see `git format-patch --range-diff=`
> 
> There are many good examples on the mailing which illustrate the above
> points; here is one such instance:
> https://lore.kernel.org/git/20240726081522.28015-1-ericsunshine@charter.net/

Thanks! I'll add this to my notes and start doing it in the next patch.

      reply	other threads:[~2024-08-13 21:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 16:31 [PATCH v6 0/8] [Newcomer] t7004: modernize the style AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 1/8] t7004: remove space after redirect operators AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 2/8] t7004: one command per line AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 3/8] t7004: do not prepare things outside test_expect_success AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 4/8] t7004: use indented here-doc AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 5/8] t7004: description on the same line as test_expect_success AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 6/8] t7004: begin the test body " AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 7/8] t7004: use single quotes instead of double quotes AbdAlRahman Gad
2024-08-08 16:32 ` [PATCH v6 8/8] t7004: make use of write_script AbdAlRahman Gad
2024-08-13 19:57 ` [PATCH v6 0/8] [Newcomer] t7004: modernize the style Eric Sunshine
2024-08-13 21:58   ` AbdAlRahman Gad [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a51779c-5404-40af-9e44-dfa05785c569@gmail.com \
    --to=abdobngad@gmail.com \
    --cc=git@vger.kernel.org \
    --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 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 NNTP newsgroup(s).