Selecting changes for splitting with crecord

[tbodt]

https://github.com/andrewshadura/git-crecord much nicer ui than the y/n/a/d prompting ui

[mystor]

Unfortunately I don't think crecord exposes an API for doing a GIT_INDEX_FILE=$INDEXFILE git reset --patch $TREE-equivalent operation, which is what would be needed to directly use it in git-revise.

That operation does an update to a specified INDEX and avoids touching the worktree. To support a tool like crecord as an alternative, it would need to either provide a low-level interface which allows doing operations like those, or we would need to re-implement the interface within git-revise.

The current cut logic is implemented here, and is fairly simple, thanks to using git reset --patch. Anything custom would be much more complex:

git-revise/gitrevise/utils.py

Lines 265 to 280 in 5d07f23

	# Create an environment with an explicit index file and the base tree.
	#
	# NOTE: The use of `skip_worktree` is only necessary due to `git reset
	# --patch` unnecessarily invoking `git update-cache --refresh`. Doing the
	# extra work to set the bit greatly improves the speed of the unnecessary
	# refresh operation.
	index = base_tree.to_index(
	commit.repo.get_tempdir() / "TEMP_INDEX", skip_worktree=True
	)
	# Run an interactive git-reset to allow picking which pieces of the
	# patch should go into the first part.
	index.git("reset", "--patch", final_tree.persist().hex(), "--", ".", stdout=None)
	# Write out the newly created tree.
	mid_tree = index.tree()