From: Kyle Meyer <kyle@kyleam.com>
To: christian w <usebees@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: ls-files bug report
Date: Wed, 05 Aug 2020 21:54:01 -0400 [thread overview]
Message-ID: <8736504k06.fsf@kyleam.com> (raw)
In-Reply-To: <CADjceoRtFmM2H1z48HcmvWBF1KmMrwMnE6YdC9HJGFjdXXivJw@mail.gmail.com>
christian w writes:
> Sorry for the insufficient reproduction steps.
>
> I managed to figure out it has something to do with git repos within
> git repos. It happened to us because of go packages that are inside
> our repo. These are the reproduction steps that work for me
> consistently using Go version go1.14.4 darwin/amd64. This is the repo
> that gets cloned into src/golang.org/x/debug by the go get command:
> https://github.com/golang/debug/tree/66ec140f2f72d15dc6133502edd2bb7238b1740c
>
> $ mkdir testdir
> $ cd testdir
> $ git init .
> $ GOPATH=$(pwd) go get -u golang.org/x/debug/ || true
> $ git ls-files --others '*.txt'#
> src/golang.org/x/debug/
Okay, removing Go from the equation:
$ # in fresh repo
$ mkdir a
$ git init a/d0
$ touch a/f0.txt
$ git ls-files --others 'a/*.txt'
a/d0/
a/f0.txt
It looks like the spurious a/d0/ entry doesn't show up until v2.27.0, in
particular 95c11ecc73 (Fix error-prone fill_directory() API; make it
only return matches, 2020-04-01). Adding the author to the Cc. (Sorry,
Elijah, I recall your frustration with dir.c from a previous ls-files
issue that I reported [1]).
[1] https://lore.kernel.org/git/CABPp-BFG3FkTkC=L1v97LUksndkOmCN8ZhNJh5eoNdquE7v9DA@mail.gmail.com/
next prev parent reply other threads:[~2020-08-06 1:54 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
2020-08-06 0:27 ` christian w
2020-08-06 1:54 ` Kyle Meyer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736504k06.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--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.
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.