From: Taylor Blau <me@ttaylorr.com>
To: Debra Obondo via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Debra Obondo <debraobondo@gmail.com>
Subject: Re: [PATCH] t7001-mv.sh:modernizing test script using function
Date: Sun, 30 Oct 2022 14:00:13 -0400 [thread overview]
Message-ID: <Y167rdL0IB5wnXHL@nand.local> (raw)
In-Reply-To: <pull.1372.git.git.1667150441883.gitgitgadget@gmail.com>
On Sun, Oct 30, 2022 at 05:20:41PM +0000, Debra Obondo via GitGitGadget wrote:
> t/t7001-mv.sh | 62 +++++++++++++++++++++++++--------------------------
> 1 file changed, 31 insertions(+), 31 deletions(-)
Looks good. Will queue, thanks.
Thanks,
Taylor
next prev parent reply other threads:[~2022-10-30 18:00 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 [this message]
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
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=Y167rdL0IB5wnXHL@nand.local \
--to=me@ttaylorr.com \
--cc=debraobondo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.
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).