@pisquaredbyi I don't need it so often, but it is perfect for finding out why something that used to work doesn't work any more. It points out exactly which commit caused the problem, which greatly narrows down the amount of code to stare at and is also useful for knowing who to ask about it.
The difference between savanna villages and other villages is that the farms try to follow the terrain, leaving exposed water. An old bug, but gets revealed in its full glory in the new 1.18 terrain.... just one of many bugs on the list :) http://pbs.twimg.com/media/FEOm2GzXIAMmSMh.jpg
Story of my day:
1: Grab a bug from the list
2: Try to solve it
3: Realize that I don't know how to fix it or it is too risky / icky to fix this now during pre-release
4: Write down what I learned about the bug, for whenever we do fix it
5: Goto 1
What's the story of your day?
@lalleal @JaredANeil I use git rebase almost every day. It is just a tool, and like any tool it can be used to solve problems or used to cause problems. There is no inherent conflict between git rebase and git bisect, it just depends on how you use it.
@BriteBytes @SemajTVLover Breakpoints pause the program and tell you what is going on. Log statements keep the program running and tell you what is going on. Sometimes I want one, sometimes the other.
devtrackers.gg
