Comment 7 for bug 1451078

There's also the poor man's version of caching (i.e what I do): keep a reasonably up-to-date branch around for when you need to do some work. That sorta works, assuming you remember to update it from time to time.

I also sometimes just commit patches directly on top of my local trunk. Then I can push it as another branch, create merge proposal, `bzr uncommit && bzr revert` locally and keep following trunk. The drawback is that if the change is not something absolutetly trivial I need to branch/get it in order to respond to code review comments. So I wouldn't necessarily recommend this strategy.