[04:58] <Azendale> So, I have a bzr branch that I'm getting ready to release to other people. The problem is that way back in the commit history there is a password in a code comment. I could take the password out today, but it would still be in the history. (In fact, there is one commit that if I could make it so that it never happened, it would be perfect). Is there a way to do this?
[04:58] <bob2_> bzr-rewrite and a lot of fiddling
[05:00] <Azendale> Ok, thought it might be using that tool, but I'm not sure I get how the big picture would work
[05:01] <Azendale> I'm guessing you branch before the bad commit
[05:02] <Azendale> but from there I'm not quite sure. But the replaying patches part of rebase sounds like what I need. I'm just not sure how you keep it from replaying the bad commit
[17:03] <leighman> get http://paste.ubuntu.com/1613366/ when trying to build with the following recipe http://paste.ubuntu.com/1613375/ any ideas?
[19:17] <ccxCZ> are there any docs on sandboxing bzr to specific repo when used via .authorized_keys/sshd_config command= directive?
[19:22]  * ccxCZ examines http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/view/head:/contrib/bzr_access