Comment 1 for bug 201409

Something does seem a little fishy here.

It seems like maybe doing a "bzr record" first would make sure that the loom state is set on disk and then the pull wouldn't overwrite it.

Regardless, it would seem that "bzr pull" shouldn't smash the target loom record. Just like we do now with file contents, 'pull' preserves local modifications.