Stefan Beller <sbeller@xxxxxxxxxx> writes:
> * "rebase -exec" requiries to be an explicit interactive rebase (i.e.
> --interactive was given)
> Could --exec just imply --interactive with a no-op editor?
Perhaps like this? You have to defend the change with a good
description, have to protect the new behaviour with a new test from
future breakages, and may have to adjust existing tests if they are
expecting the current behaviour (I didn't test).
git-rebase.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/git-rebase.sh b/git-rebase.sh
index cf60c43..c68baa0 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -248,6 +248,7 @@ do
;;
--exec=*)
cmd="${cmd}exec ${1#--exec=}${LF}"
+ interactive_rebase=explicit
;;
--interactive)
interactive_rebase=explicit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html