Stefan Beller <[email protected]> writes:
> In the later steps of preparing a patch series I do not want to edit the
> patches any more, but just make sure the test suite passes after each
> patch. Currently I would run
>
> EDITOR=true git rebase -i <anchor> -x "make test"
Hmm, I guess that may "work" but it sounds like quite a roundabout
way to "test all commits". "rebase" is about replaying history to
end up with a set of newly minted commits, and being able to poke at
the state each commit records in the working tree is a side effect.
"rebase -i" may use the same commit object if you didn't actually
make new commit as an optimization, but otherwise, it is like going
through pages of a book, tearing each page to examine it, and
replacing each page with a photocopy of it before going to examine
the next page. Which makes me feel somewhat dirty X-<.
In other words, that looks like a workaround for not having
$ git for-each-rev -x "$command" old..new
where you can write "sh -c 'git checkout $1 && make test' -" as
your $command.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
