[02:14] <KombuchaKip> Thoughts? https://bugs.launchpad.net/bzr/+bug/1077521
[23:35] <Sebboh> Months ago, I did bzr branch lp:leo-editor, or something like that.  Today I want to update my working copy with the latest changes from the same place I got the content from originally.  Unfortunately, I tried a few commands and left my workspace in some modified state.
[23:35] <Sebboh> How can I discard every local change and update to the latest revision?
[23:38] <Sebboh> After doing a bzr revert, bzr status still shows modified: .. and then lists what seems to be every file, with an * after each one.
[23:39] <fullermd> That would be +/-x, so some mismatch with the FS.
[23:40] <Sebboh> When you say +/-x, does that mean the executable bit doesn't match?
[23:41] <spiv> Right.
[23:41] <spiv> I'd have expected bzr revert to fix that, though :/
[23:42] <spiv> But if it doesn't, you could manually flip the x bit on those files.
[23:42] <Sebboh> It can't.  Fake filesystem, ignores calls to chmod.  :)  I'll move the repo to a proper filesystem and try again...
[23:43] <fullermd> That would be why revert doesn't get it to expected  :)
[23:43] <spiv> Ah, no wonder bzr revert can't fix it then :)
[23:43] <Sebboh> (virtualbox host<-->guest filesystem sharing between win7 host and debian guest. Work computer.. :P )
[23:43] <Sebboh> Yes. :)
[23:45] <Sebboh> incidentally, bzr is much faster on ext4.
[23:45] <Sebboh> hardlinks?