Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That sounds more complicated than git bisect. When I bisect I have a short test script that confirms the bug. Usually, I already have this because part of the bug report/identification. I then run "git bisect run path/to/bug.sh". That's it -- it will output which commit caused the change. Those occasional times I need to confirm the presence of actual text, I use sh -c "git grep ..." as the test command.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: