From: William Baker <williamtbakeremail@gmail.com>
To: William Baker via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: williamtbakeremail@gmail.com, Junio C Hamano <gitster@pobox.com>,
William Baker <William.Baker@microsoft.com>,
stolee@gmail.com, Johannes.Schindelin@gmx.de,
jeffhost@microsoft.com
Subject: Re: [PATCH 1/1] t7519-status-fsmonitor: improve comments
Date: Tue, 29 Oct 2019 13:07:17 -0700 [thread overview]
Message-ID: <3e95662d-3c65-8511-a01b-226b0e572b83@gmail.com> (raw)
In-Reply-To: <85ca71fadaa7390a32218d3a5553c83d60c06a7f.1571254547.git.gitgitgadget@gmail.com>
On 10/16/19 12:35 PM, William Baker via GitGitGadget wrote:
> From: William Baker <William.Baker@microsoft.com>
>
> The comments for the staging/unstaging test did not accurately
> describe the scenario being tested. It is not essential that
> the test files being staged/unstaged appear at the end of the
> index. All that is required is that the test files are not
> flagged with CE_FSMONITOR_VALID and have a position in the
> index greater than the number of entries in the index after
> unstaging.
>
> The comment for this test has been updated to be more
> accurate with respect to the scenario that's being tested.
>
> Signed-off-by: William Baker <William.Baker@microsoft.com>
> ---
> t/t7519-status-fsmonitor.sh | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/t/t7519-status-fsmonitor.sh b/t/t7519-status-fsmonitor.sh
> index d8df990972..997d5fb349 100755
> --- a/t/t7519-status-fsmonitor.sh
> +++ b/t/t7519-status-fsmonitor.sh
> @@ -354,9 +354,11 @@ test_expect_success 'discard_index() also discards fsmonitor info' '
> test_cmp expect actual
> '
>
> -# Test staging/unstaging files that appear at the end of the index. Test
> -# file names begin with 'z' so that they are sorted to the end of the index.
> -test_expect_success 'status succeeds after staging/unstaging ' '
> +# Test unstaging entries that:
> +# - Are not flagged with CE_FSMONITOR_VALID
> +# - Have a position in the index >= the number of entries present in the index
> +# after unstaging.
> +test_expect_success 'status succeeds after staging/unstaging' '
> test_create_repo fsmonitor-stage-unstage &&
> (
> cd fsmonitor-stage-unstage &&
>
Gentle ping on this patch. It's just a small update to the comments
for an fsmonitor related test based on feedback I received in the
segfault fix patch series [1].
Thanks,
William
[1] https://public-inbox.org/git/3d3b290c-bc15-4bd5-e0c0-1377c9ec3ff9@gmail.com/
next prev parent reply other threads:[~2019-10-29 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 19:35 [PATCH 0/1] t7519-status-fsmonitor: improve comments William Baker via GitGitGadget
2019-10-16 19:35 ` [PATCH 1/1] " William Baker via GitGitGadget
2019-10-29 20:07 ` William Baker [this message]
2019-10-30 2:52 ` Junio C Hamano
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=3e95662d-3c65-8511-a01b-226b0e572b83@gmail.com \
--to=williamtbakeremail@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=William.Baker@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=stolee@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 NNTP newsgroup(s).