What does HackerNews think of git-series?

Track changes to a patch series over time

Language: Rust

Yet another meta-history tool, but this one is a supposed to be rolled into git(1) itself, so that tools like git-commit, git-rebase, and others will work with it.

See also: https://github.com/git-series/git-series/

See also: `git range-diff` used between versions of a branch (regular branches: manual checkouts like `feature-v3`)

See also: probably others

In the current model every plugin you'd have in your repo would have to be aware of your plugin manager, right?

I suspect you'd need adoption before authors would want to maintain a Pluginfile.json, and before there's a decent selection in your repo there's not a selling point to gain adoption.

A tool that can help me find things like git-series[0] would be cool, but I think you'd need to work downstream rather than having every git plugin know about your package manager. If you're gonna make repos to wrap upstream projects into your package format (which is what Linux distros do), then that could work.

[0]: https://github.com/git-series/git-series

The idea of commit groups makes me think of Linux kernel style patch series and https://github.com/git-series/git-series
> We are planning to reimplement the current featureset in a more robust language.

I saw on your projects list that you plan to port it from shell to Rust. Nice choice. I had a great experience using Rust for git-series (https://github.com/git-series/git-series/ ); the git2-rs binding is a joy to use.

If you run into any issues along the way, or want some help with git2-rs, I'd be happy to chat about it. (And, of course, feel free to borrow anything from git-series; if you find something useful and non-trivial that you'd like to share, let me know and I can extract it into a crate.)