git bisect with additional patch -


let's have these revisions:

  • rev 1 introduces bug #1
  • rev 2 possibly introduces bug #2
  • rev 3 possibly introduces bug #2
  • rev 4 possibly introduces bug #2
  • rev 5 fixes bug #1

to verify bug #2 occured, bug #1 needs fixed.

can revision bug #2 first occured determined during single git bisect run, possibly through manually appling rev 5 patch on each bisect step? manually patching interfere bisect?

after reading docs, might work (per bisect step):

git cherry-pick [patch-rev] git reset --hard git bisect [good/bad] 

Comments

Popular posts from this blog

java - Spring Data JPA: Why findOne(id) executing delete query internally? -

python - Mongodb How to add addtional information when aggregating? -

java - Incorrect order of records in M-M relationship in hibernate -