toolgit VS git-blameall

I like these a lot! It seems like git-extras is pure bash allowing it to work out of the box without any dependencies but I would probably go mad if I had to implement¹ reading/writing git index² in bash.

[¹]: https://github.com/ahmetsait/toolgit/blob/58713ead5abc060510...

I've been carrying around a copy of "git blameall" for years - looks like https://github.com/gnddev/git-blameall is the same one - that basically does this, but keeps it all interleaved in one output (which works pretty well for archeology, especially if you're looking at "work hardened" code.)

(Work hardening is a metalworking term where metal bent back and forth (or hammered) too much becomes brittle; an analogous effect shows up in code, where a piece of code that has been bugfixed a couple of times will probably be need more fixes; there was a published result a decade or so back about using this to focus QA efforts...)

The most useful git extra command I know of is git blameall from https://github.com/gnddev/git-blameall but apparently it's just me because when the time came I needed to port it to Python 3 but oh well :)

Here's a part of Drupal index.php: https://i.imgur.com/Xw4OAEC.png

Thanks, I knew about -committerdate but not that you can set it as default sort, super useful. A few notes...

1. git columns gets real confusing if you have more data than fits the screen and you need to scroll. Numbers would help...

2. git maintenance sounds great but since I do a lot of rebases and stuff, I am worried: does this lose loose objects faster than gc would? I see gc is disabled but it's not clear.

3. Regarding git blame a little known but super useful script is https://github.com/gnddev/git-blameall . (I mean, it's so little known I myself needed to port it to Python 3 and I am no Python developer by any stretch.)

The author mentions git blame which is indeed an important tool but in more complex codebases it's entire possible the original introduction would require several steps because the code was refactored since. For this, git blameall is a wonderful and almost completely unknown utility. https://github.com/gnddev/git-blameall Yours truly did a quick Python 3 port this January, mostly using the automated toolset for it and the author, much to my surprise, committed it in a week despite the last commit was in 2013. So the project is not dead :)

Does anyone know whether git blameall https://github.com/ddev/git-blameall is easy to do with Fossil? It's a lesser known tool but I found it incredibly useful (hence why I did the Python 3, mostly automated tools but still).