[01:23] <mtaylor> bzr: ERROR: bzrlib.errors.ShortReadvError: readv() read 72 bytes rather than 805 bytes at 0 for "edc52d2d94b242f1cd3a2ccac6e0dad5.tix"
[04:27] <sili> Is there a clever way to show a diff of changes since the branch was created?
[04:31] <sili> doing a diff against the parent branch works, but doesn't offer the results I want after the branch has already been merged, so I usually have to specify the revision it was branched at
[08:36] <spiv> sili: bzr diff -rancestor::parent
[08:39] <spiv> (If the parent branch is also the submit branch, then "bzr diff -r submit:" is a shorter way to do the same thing)
[10:40] <sili> spiv: what does it mean if that doesn't show any diff?
[10:57] <spiv> sili__: that there's no change in the tree contents between the revision you branched from and the current revision
[10:58] <spiv> sili__: perhaps look at the output of "bzr missing --mine", or perhaps look at the locations listed in "bzr info" if that isn't what you expect
[11:00] <spiv> If this is a branch intended for merging into another, perhaps see what 'bzr merge --preview YOUR_BRANCH' in a checkout/branch of the target branch is.
[13:06] <sili__> hmmm
[16:10] <damd> what is the difference between "bzr update" and "bzr pull"?
[16:10] <damd> the former takes several megabytes more than the latter when performed on emacs trunk
[18:40] <mtaylor> anybody have any idea what bzr: ERROR: bzrlib.errors.ShortReadvError: readv() read 72 bytes rather than 805 bytes at 0 for "edc52d2d94b242f1cd3a2ccac6e0dad5.tix" is about?
[18:42] <mtaylor> oh - nevermind... wft?
[22:52] <timClicks> noob q: is it possible to delay committing some changes to the next commit? I have changed two files and would like to spread the changes between two commits because they don't have much to do with each other