3 ms·
When I make Bash aliases or functions for Git functionality, I always name them as `git-something-or-other`. That way they're namespaced in a way that I find pl
by zahlman 1y ago
When I make Bash aliases or functions for Git functionality, I always name them as `git-something-or-other`. That way they're namespaced in a way that I find pleasant both for tab completion and for easy of memory. I think that should apply to more complex utilities, too.
By my usual naming conventions, this one would be `git-repeatedly-changed`.
- nothrabannosir 1y agoLast but decidedly not least: if you have `git-foo` on the PATH, you can do `git foo` and it will automatically pick up your program. If I remember early git days correctly, that's how git was implemented: a bunch of separate utilities working together on the database which is the .git folder.
- gavmor 1y agoThese are called alternative "porcelains:"[0] third-party, user-friendly interfaces built on top of Git's stable, low-level plumbing commands. 0. https://git-scm.com/docs/git.html#_low_level_commands_plumbing https://git-scm.com/docs/git.html#_low_level_commands_plumbi...
- mjd 1y agoI usually do that too, but this seemed to me like it's not really a git utility. It's just a filter. I can see the argument in favor of `git-` also. But I think I'd prefer `git-changed-twice` to be a wrapper that takes a reflist argument, and runs `git-log --stat reflist | what-changed-twice`.