# Retrieving logs matching pattern for all time.

3 messages from 2011-09-03 to 2011-09-04. Participants: Jeremy Nickurak, Thomas Rast, Junio C Hamano.
Thread: https://gitlist.dev/t/28290

## Jeremy Nickurak, 2011-09-03 00:03

Subject: Retrieving logs matching pattern for all time.
Message-ID: <CA+eQo_0gZpbz399GN1b+0mq8OY3Xoo+kij=UGSjwbJcNreYBvw@mail.gmail.com>
URL: https://gitlist.dev/e/CA%2BeQo_0gZpbz399GN1b%2B0mq8OY3Xoo%2Bkij%3DUGSjwbJcNreYBvw%40mail.gmail.com

```
I have a glob pattern of files, and I'd like to get git logs for every
commit that touched those files. 'git log filesmatchingglob*' is
pretty close.

Unfortunately, because the * is interpreted by bash, it doesn't catch
logs for files that don't exist anymore.

Protecting the * from bash was my next thought, but that doesn't seem to help:

> user@host:~$ mkdir something
> user@host:~$ cd something
> user@host:~/something$ git init
> Initialized empty Git repository in /home/nickuj/something/.git/
> user@host:~/something$ echo hello > hello.txt
> user@host:~/something$ git add hello.txt
> user@host:~/something$ git commit -m hello hello.txt
> [master (root-commit) ca4b223] hello
>  1 files changed, 1 insertions(+), 0 deletions(-)
>  create mode 100644 hello.txt
> user@host:~/something$ git log -- 'hel*'
> user@host:~/something$

IE, git doesn't seem to interpret globs itself in patterns.

http://stackoverflow.com/questions/543346/git-list-all-the-files-that-ever-existed
suggests a means to get a list of all files that ever existed, and I
could certainly iterate across that, find the files that match the
pattern, and then run git-log against that.... but it seems like a
problem somebody's already solved more elegantly.

Any thoughts?

-- 
Jeremy Nickurak

```

## Thomas Rast, 2011-09-04 16:13

Subject: Re: Retrieving logs matching pattern for all time.
Message-ID: <201109041813.24418.trast@student.ethz.ch>
URL: https://gitlist.dev/e/201109041813.24418.trast%40student.ethz.ch
In-Reply-To: <CA+eQo_0gZpbz399GN1b+0mq8OY3Xoo+kij=UGSjwbJcNreYBvw@mail.gmail.com>

```
Jeremy Nickurak wrote:
> > user@host:~/something$ git log -- 'hel*'
> > user@host:~/something$
> 
> IE, git doesn't seem to interpret globs itself in patterns.

It does for me:

thomas@thomas:~/g(next u+59)$ g log --oneline --name-status -- "REA*"
f73b3af README: git lives at http://git-scm.com these days
M       README

etc.

Which git version are you using?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

```

## Junio C Hamano, 2011-09-04 18:59

Subject: Re: Retrieving logs matching pattern for all time.
Message-ID: <7vy5y4yvzl.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vy5y4yvzl.fsf%40alter.siamese.dyndns.org
In-Reply-To: <201109041813.24418.trast@student.ethz.ch>

```
Thomas Rast <trast@student.ethz.ch> writes:

> Jeremy Nickurak wrote:
>> > user@host:~/something$ git log -- 'hel*'
>> > user@host:~/something$
>> 
>> IE, git doesn't seem to interpret globs itself in patterns.
>
> It does for me:
>
> thomas@thomas:~/g(next u+59)$ g log --oneline --name-status -- "REA*"
> f73b3af README: git lives at http://git-scm.com these days
> M       README
>
> etc.

The "git log" family learned globbing pathspecs in 1.7.5 if I believe the
Release Notes.

```