From: Nguyen Thai Ngoc Duy Date: Sat, 12 May 2012 15:40:49 GMT Subject: Re: ls-tree and wildcards Message-ID: In-Reply-To: <4FAE7CBD.3020605@rotorised.com> On Sat, May 12, 2012 at 10:07 PM, Ryan McCue wrote: > Good evening folks, > > I'm attempting to grab relevant information for files in a tree matching a > given pattern with wildcards. The help for ls-tree indicates that it can > accept a pattern of files to match, however I'm not able to see that. > > $ git ls-tree origin/master > ... > 100644 blob 8c391e8fb44a38e1389a710ebf8af79612e592a6    screenshot-1.png > 100644 blob ecb7159c1c02567e9cd5da83c254c538d331f733    screenshot-2.png > 100644 blob f58eea7e27f98c01038262b823aa73ccd64cb01e    screenshot-3.png > 100644 blob 07e64def408145660cee657a46947077374762cc    screenshot-4.png > $ git ls-tree origin/master screenshot* > $ > > (I've also tried quoting to ensure it's not bash playing up) > > Is there some issue with the command I'm issuing? The documentation seems to > indicate that I should be getting back the files which match the pattern. I don't think it ever does. There's a mention of "patterns" in ls-tree man page, which is misleading. We have the facilities to do that now ("lstree -r patterns" actually) but that might break backward compatibility. For now I guess you can just do GIT_INDEX_FILE=/tmp/some-temporary-index git read-tree origin/master GIT_INDEX_FILE=/tmp/some-temporary-index ls-files A question that might help us understand your use case and give a better advice, or improve the system: why do you need that? -- Duy