> So on my computer, the 1st test fails (dunno why, I'm running from bzr),
Ahhh, I'm using co-located branches (attempting to lessen the cognitive load of using bzr, hg & git depending on which project I'm tracking), so the last-revision file is not in the expected place. Expected: leo\.bzr/branch/last-revision Actual: leo\.bzr\branches\doc-edits\.bzr\branch\last-revision leo\.bzr\branches\origin\trunk\.bzr\branch\last-revision So we could chalk this one up to my fault for departing from Leo bzr standard practice, but it will likely happen to someone else down the road, so documenting here for posterity (e.g. me, at next release!) The real question is: what do we need to do to ensure that updating bzr_version.py doesn't rely on frail human memory? (or, why do we need it anyway, since it so rarely actually reflects the real bzr version?) -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
