git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe Crino' <giuscri@gmail.com>
To: git@vger.kernel.org
Subject: Re: git can't add ignored file if GIT_ICASE_PATHSPECS=1
Date: Tue, 12 Feb 2019 18:27:09 +0100	[thread overview]
Message-ID: <20190212172708.GA506@evil.localdomain> (raw)
In-Reply-To: <20190212171952.GA343@evil.localdomain>

I forgot to mention that the issue is present both in maint and in the master branch.

On Tue, Feb 12, 2019 at 06:19:52PM +0100, Giuseppe Crino' wrote:
> To reproduce, apply the attached patch and run at the project root
> 
> 	cd t && ./t3700-add.sh --verbose-only=13 --debug --immediate
> 
> Relevant part of the output is
> 
> 	expecting success:
> 		export GIT_ICASE_PATHSPECS=1 &&
> 		touch a.if &&
> 		test_must_fail git add a.?? &&
> 		! (git ls-files | grep "\\.ig") &&
> 		(git ls-files | grep a.if)
> 
> 	fatal: pathspec 'a.ig' did not match any files
> 	not ok 13 - error out when attempting to add ignored ones but add others
> 	#
> 	#               export GIT_ICASE_PATHSPECS=1 &&
> 	#               touch a.if &&
> 	#               test_must_fail git add a.?? &&
> 	#               ! (git ls-files | grep "\\.ig") &&
> 	#               (git ls-files | grep a.if)
> 
> As I understand this, it's a bug.
> 
> Giuseppe

> diff --git a/t/t3700-add.sh b/t/t3700-add.sh
> index 37729ba258..62557e6a3d 100755
> --- a/t/t3700-add.sh
> +++ b/t/t3700-add.sh
> @@ -91,6 +91,7 @@ test_expect_success 'error out when attempting to add ignored ones without -f' '
>  '
> 
>  test_expect_success 'error out when attempting to add ignored ones but add others' '
> +       export GIT_ICASE_PATHSPECS=1 &&
>         touch a.if &&
>         test_must_fail git add a.?? &&
>         ! (git ls-files | grep "\\.ig") &&


      reply	other threads:[~2019-02-12 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 17:19 git can't add ignored file if GIT_ICASE_PATHSPECS=1 Giuseppe Crino'
2019-02-12 17:27 ` Giuseppe Crino' [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=20190212172708.GA506@evil.localdomain \
    --to=giuscri@gmail.com \
    --cc=git@vger.kernel.org \
    /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).