From: "Martin Ågren" <martin.agren@gmail.com>
To: Debra Obondo via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
Debra Obondo <debraobondo@gmail.com>
Subject: Re: [PATCH v2] t7001-mv.sh: modernizing test script using functions
Date: Thu, 3 Nov 2022 20:37:21 +0100 [thread overview]
Message-ID: <CAN0heSohT_zDYequyv9-cCALrbpR0yQnSoPA3+YGMhgKxE5K3g@mail.gmail.com> (raw)
In-Reply-To: <pull.1372.v2.git.git.1667500788132.gitgitgadget@gmail.com>
On Thu, 3 Nov 2022 at 19:39, Debra Obondo via GitGitGadget
<gitgitgadget@gmail.com> wrote:
>
> From: Debra Obondo <debraobondo@gmail.com>
>
> Test script to verify the presence/absence of files, paths, directories,
> symlinks and other features in 'git mv' command are using the command
> format:
>
> 'test (-e|f|d|h|...)'
>
> Replace them with helper functions of format:
>
> 'test_path_is_*'
Ok.
> Changes since v1
>
> Replacing idiomatic helper functions
>
> '! test_path_is_*'
>
> with
>
> 'test_path_is_missing'
>
The above "Changes since v1" and what I've quoted here should probably
be dropped. We prefer our patches to look as if they've appeared out of
the blue in perfect shape. :-)
> This uses values of 'test_path_bar' in place of '! test_path_foo' to
> bring in the helpful factor of indicating the failure of tests after the
> mv command has been used, that is, it echoes if the feature/test_path
> exists.
This paragraph is excellent. It describes why you've done the patch this
way. This looks much better than version 1 of the patch!
> Signed-off-by: Debra Obondo <debraobondo@gmail.com>
After removing the lines about changes since v1, this patch is
Reviewed-by: Martin Ågren <martin.agren@gmail.com>
> ---
> [PATCH v2] [OUTREACHY] t7001-mv.sh : Use test_path_is_* functions in
> test script
>
> Changes since v1:
>
> Replacing idiomatic helper functions
>
> '! test_path_is_*'
>
> with
>
> 'test_path_is_missing'
This place after the "---" line is an excellent place for including such
"here's what has changed since v1" comments. Good. They will not appear
in the final commit message.
Thanks for contributing!
Martin
next prev parent reply other threads:[~2022-11-03 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 17:20 [PATCH] t7001-mv.sh:modernizing test script using function Debra Obondo via GitGitGadget
2022-10-30 18:00 ` Taylor Blau
2022-10-31 18:04 ` Martin Ågren
2022-11-01 1:14 ` Taylor Blau
2022-11-03 18:39 ` [PATCH v2] t7001-mv.sh: modernizing test script using functions Debra Obondo via GitGitGadget
2022-11-03 19:37 ` Martin Ågren [this message]
2022-11-04 15:05 ` [PATCH v3] " Debra Obondo via GitGitGadget
2022-11-04 22:00 ` Taylor Blau
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=CAN0heSohT_zDYequyv9-cCALrbpR0yQnSoPA3+YGMhgKxE5K3g@mail.gmail.com \
--to=martin.agren@gmail.com \
--cc=debraobondo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.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.