konglu@xxxxxxxxxxxxxxx writes:
>> +You may execute several commands by either using one instance of `--exec`
>> +with several commands:
>> +
>> -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 && cmd2 && ..."
>> +
>> - git rebase -i --exec "cmd1" --exec "cmd2" ...
>> +or equivalently by giving more than one `--exec`:
>
> ...I'm against using "equivalently" as in the first case, all the commands
> are on one line, and in the second case, each commands have its line, thus
> easier for the user to manipulate them independently.
It looks that editing
pick foo pick foo
exec cmd1 exec cmd1 && cmd2
exec cmd2
pick bar pick bar
exec cmd1 exec cmd1 && cmd2
exec cmd2
to
pick foo pick foo
exec cmd2
exec cmd2
pick bar pick bar
exec cmd1 exec cmd1
would take exactly the same effort, at least to me. And more
importantly, without editing don't they do *exactly* the same thing?
If cmd1 fails, the sequencing stops at that step without running cmd2.
--
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