From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Emily Xie <emilyxxie@gmail.com>,
git@vger.kernel.org, David Turner <novalis@novalis.org>
Subject: Re: [PATCH] pathspec: die on empty strings as pathspec
Date: Fri, 23 Jun 2017 13:59:38 -0700 [thread overview]
Message-ID: <xmqqr2yactdx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <802ccd37-c09a-8343-63fe-a42c682a8311@web.de> ("Torsten Bögershausen"'s message of "Fri, 23 Jun 2017 22:52:44 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> On 23/06/17 20:04, Junio C Hamano wrote:
>...
>> At this point in the test sequence, there is no modified path that
>> need to be further added before committing; the working tree is
>> empty except for .gitattributes which was just added to the index.
>> So we could instead pass no pathspec, but this is a conversion more
>> faithful to the original.
>>
>> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>> ---
>> t/t0027-auto-crlf.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/t/t0027-auto-crlf.sh b/t/t0027-auto-crlf.sh
>> index 93725895a4..e41c9b3bb2 100755
>> --- a/t/t0027-auto-crlf.sh
>> +++ b/t/t0027-auto-crlf.sh
>> @@ -322,7 +322,7 @@ test_expect_success 'setup master' '
>> echo >.gitattributes &&
>> git checkout -b master &&
>> git add .gitattributes &&
>> - git commit -m "add .gitattributes" "" &&
>> + git commit -m "add .gitattributes" . &&
>
> Reading the context here, there shouldn't be a "pathspec" at all,
> as .gitattributes had been added just one line above.
>
> The line should have been from the very beginning:
> git commit -m "add .gitattributes" &&
>
> # What do you think ?
See above ;-)
And to be more explicit, it is not a fault of your earlier change,
either, that we didn't notice this problem since we started "warning".
We need to see if we can update our test framework to help us
better; I really think the test framework could and should have
helped us to notice this soon after we went into "keep behaving as
before but warn" stage.
prev parent reply other threads:[~2017-06-23 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 3:33 [PATCH] pathspec: die on empty strings as pathspec Emily Xie
2017-06-09 16:28 ` Junio C Hamano
2017-06-10 6:21 ` Jeff King
2017-06-10 11:03 ` Junio C Hamano
2017-06-09 16:50 ` Brandon Williams
2017-06-10 5:54 ` Junio C Hamano
2017-06-23 2:34 ` Emily Xie
2017-06-23 4:09 ` Junio C Hamano
2017-06-23 4:46 ` Junio C Hamano
2017-06-23 18:04 ` Junio C Hamano
2017-06-23 20:52 ` Torsten Bögershausen
2017-06-23 20:59 ` Junio C Hamano [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=xmqqr2yactdx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=emilyxxie@gmail.com \
--cc=git@vger.kernel.org \
--cc=novalis@novalis.org \
--cc=tboegi@web.de \
/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.