Lucien Kong <Lucien.Kong@xxxxxxxxxxxxxxx> writes: > @@ -210,11 +210,29 @@ rebase.autosquash:: > > OPTIONS > ------- > -<newbase>:: > - Starting point at which to create the new commits. If the > - --onto option is not specified, the starting point is > - <upstream>. May be any valid commit, and not just an > - existing branch name. > +-x <cmd>:: > +--exec <cmd>:: > + Automatically add "exec" followed by <cmd> between each commit > + applications. Using this option along with --autosquash adds > + the exec line after the squash/fixeup series only. <cmd> > + stands for shell commands. The --exec option has to be > + specified. (see INTERACTIVE MODE below) It would make sense to split that into two patches, one to fix --onto's documentation, and the next one to add --exec. I won't insist on that though (but maybe others will). > ++ > +This has to be used along with the `--interactive` option explicitly. > +You may execute several commands between each commit applications. > +For this, you can use one instance of exec: > + git rebase -i --exec "cmd1; cmd2; ...". > +You can also insert several instances of exec, if you wish to > +only have one command per line for example: > + git rebase -i --exec "cmd1" --exec "cmd2" ... This formats badly in asciidoc (try "make doc" and see the generated HTML). Try this: This has to be used along with the `--interactive` option explicitly. You may execute several commands between each commit applications. For this, you can use one instance of exec: + git rebase -i --exec "cmd1; cmd2; ...". + You can also insert several instances of exec, if you wish to only have one command per line for example: + git rebase -i --exec "cmd1" --exec "cmd2" ... -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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