Post Syndicated from original https://lwn.net/Articles/914041/

The Git source-code management system exists to track changes to a set of
files; the stream of commits in a Git repository
reflects the change history of those files. What is seen in Git, though, is the
final form of those commits; the changes that the patches themselves went
through on their way toward acceptance are not shown there. That history
can have value, especially while changes are still under consideration.
The proposed git
evolve subcommand is a recognition that changes themselves go
through changes and that this process might benefit from tooling support.