On Wed, Jul 28, 2010 at 3:29 PM, Matthieu Moy <Matthieu.Moy@xxxxxxx> wrote: > The typical usage pattern would be to run a test (or simply a compilation > command) at given points in history. > > The shell command is ran, and the rebase is stopped when the command > fails, to give the user an opportunity to fix the problem before > continuing with "git rebase --continue". > I think this is a useful addition, but I would find it more useful if I could run a command (make test) on top of all commits of a patch series, like: $ git run HEAD^4.. command arguments (I'm not quite sure about the syntax). Something like "git bisect run" but for all the commits in the range. I know you said "given points in history", maybe each approach is useful for each use case. Thanks, Santi -- 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