>> So something between 1.5.6.5 and 1.6.0-rc0 broke it for me. >> A quick diff between the two version revealed a lot of changes. Thus >> tracking down the issue might not be easy for someone who is not >> involved >> in the code. > > Start with: > > $ git bisect start v1.6.0-rc0 v1.5.6.5 v1.6.0~6^2 v1.6.0.2~16^2 # [*] > > and test the version that this command gives you. Then say either > > $ git bisect good # if the version works > $ git bisect bad # if the version fails > > Test again and repeat until the command tells you "First bad revision > is..." and report back. (Finally, say 'git bisect reset' to get you back > to where you started.) > > [*] The revisions v1.6.0~6^2 v1.6.0.2~16^2 are from gitk and git-gui, > which we assume are good. > > -- Hannes Wow, thank you Hannes! Will do so. -- 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
