Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > Santi Béjar <santi@xxxxxxxxxxx> writes: > >> $ 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. > > Yes, I think both approaches make sense. I started playing with the patch, and I'm already starting to love it ;-). For example pick <commit1> fixup <commit4> run make pick <commit2> pick <commit3> ... Just does "the right thing": it checks that the fixup doesn't break the commit (which is really not only a new state, but also a new patch, so it can really break), but doesn't spend too much time re-checking <commit2> and <commit3> (which are new states, but much more trustworthy than the fixup since the patches are really the same. I may check them later, but don't want to lose time with them while hacking). -- 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