Hacker News new | ask | show | jobs
by weebst 456 days ago
That's a neat idea, I can see how it'd be useful.

If you have a shell that supports extended globbing, you could do something like:

  $ git who table */**/*.go
That works for me using Bash. I believe all that's happening here is that Bash is expanding the globs and passing a long list of individual filepaths as arguments to git who. Git who then passes them to git log so that it only tallies the commits you'd get by running:

  $ git log */**/*.go
2 comments

Yup. It’s a complex enough set of in/excludes that I think that would get unwieldy for my use case.

Details here:

https://github.com/Aider-AI/aider/blob/main/scripts/blame.py

Again, nice work on your tool. I’ll spend some more time trying to harness it for my need.

Thank you very much!
> $ git who table */**/*.go

I might have my globbing syntax wrong, but I think that `*/**/*.go` is the same as `**/*.go` unless you have `*.go` files in the working directory.