From: "Russ P" <>
I am working independently on a software project, and I am a novice git
user, using only a few basic commands (status, diff, add, commit, checkout,
and log).

I got myself into a bit of a jam. I did a redesign on part of my code, and
I introduced a subtle but major bug somewhere. I was doing a few basic
tests after each small change, but those tests did not catch the bug that I
had introduced. To make matters worse, I waited too long between commits
(almost a week). Now I have a bug that I can isolate to a particular
commit, but the commit was large, and I cannot pinpoint the bug.

I've tried many things to no avail. At this point, I think I need to revert
back to the last working version and then try to add the changes back in
piecemeal until I locate the offending code. However, I am a bit unsure
about the best way to do that with git. I know how to checkout the last
working version and then go back to the latest code by checking out master.
But what will happen if I start making changes to the earlier working
version? Is this something that I should be using a branch for? What is the
best strategy? Thanks.

My "off the top of the head" view would be one of:
a. create a temp branch at the current branch head, then deliberately 'rebase -i' the sequence including the bad commit onto it's parent commit. Mark the bad commit as 'edit', and after it has been rebased, at the edit, amend that last commit to split it into multiple parts, letting the remainder rebase as normal. You'll now have a temp branch that can be bisected.

b. create a temp branch at the parent of the bad commit, cherry-pick the bad commit and then amend / patch pick the constituent parts of that commit, now rebase the remaining commits onto that branch. Again you have a bisectable sequence with more fine grain selection within the bad commit. Repeat as needed.

You received this message because you are subscribed to the Google Groups "Git for 
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to