From: Kyle Meyer <kyle@kyleam.com>
To: christian w <usebees@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ls-files bug report
Date: Wed, 05 Aug 2020 19:59:33 -0400 [thread overview]
Message-ID: <878ses4pay.fsf@kyleam.com> (raw)
In-Reply-To: <CADjceoQxoL932W4mkfhG6VOgrQBhs9k6tXkWSkraKVPmUP+uCw@mail.gmail.com>
christian w writes:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> git ls-files --others 'some/path/*.some.extension'
>
> What did you expect to happen? (Expected behavior)
>
> only list files under some/path/ that had .some.extension
>
> What happened instead? (Actual behavior)
>
> It listed those files and also all untracked folders underneath some/path/
I tried to follow your description, and I don't see this on my end. In
a fresh repository:
$ mkdir -p some/path/d0
$ mkdir -p some/path/d1
$ touch some/path/f0 some/path/d0/f0 some/path/f1.some.extension
$ git ls-files --others
some/path/d0/f0
some/path/f0
some/path/f1.some.extension
$ git ls-files --others 'some/path/*.some.extension'
some/path/f1.some.extension
$ git version
git version 2.28.0
Could you provide a more detailed recipe to reproduce the issue?
> [System Info]
> git version:
> git version 2.28.0
next prev parent reply other threads:[~2020-08-05 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 15:15 ls-files bug report christian w
2020-08-05 23:59 ` Kyle Meyer [this message]
2020-08-06 0:27 ` christian w
2020-08-06 1:54 ` Kyle Meyer
2020-08-07 4:10 ` Elijah Newren
2020-08-12 14:50 ` Elijah Newren
2020-08-12 17:48 ` christian w
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ses4pay.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=git@vger.kernel.org \
--cc=usebees@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).