weebst
The Trellis: A Gardening Metaphor for Software Engineering
Glfmn.io Blog Links
Not sure what's happening with the tarball. Will take a look at that.
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 */**/*.goShow HN: "Git who" – A new CLI tool for industrial-scale Git blaming
https://github.com/sinclairtarget/git-who
I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this.It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options.If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!
If you think you'd enjoy long-form, deeply researched essays that look at the development of technical ideas throughout the history of computing, I've got you covered.