Rodrigo recently asked me about this, and I totally failed to properly document it!
Cc: Rodrigo Vivi <rodrigo.v...@intel.com> Signed-off-by: Daniel Vetter <daniel.vet...@intel.com> --- qf | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/qf b/qf index 31b9f3bae0a2..883dda0a1668 100755 --- a/qf +++ b/qf @@ -540,6 +540,25 @@ $ qf git pull && qf checkout test Doing only a git pull on the quilt branch leads to an inconsitent state if the baseline changed. +Bisecting patch history +----------------------- + +Git history in the patches directory records every rebase or any other changes +to the patch pile, including the baseline. Which means it can be used for +bisecting not just the individual patches, but the history of the entire patch +pile: + +$ qf git bisect *old-sha1* *new-sha1* + +to start the bisect process, and then for each bisect step: + +$ qf checkout HEAD + +Run tests to figure out whether it's part of the new (bad) or old (good) +history, then tell git using + +$ qf git bisect new|old + COMMANDS ======== -- 2.7.4 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
