On 8/25/09, Edward K. Ream <[email protected]> wrote: > The problem with caching is perhaps only a symptom of a deeper > problem, namely, how to synchronize leoProjects.txt. This problem > gets quite severe when working on several branches at once. It's > gotten so bad that I don't want to drag info into leoProjects.txt, but > that's not good either: it's too easy to lose info (the view, not the > actual nodes) when using bzr pull --overwrite.
I think it's safer to ignore "reference" thin files when doing a merge. Just use the version of the reference file you deem more valuable and throw the other one away, merging the diffs feels risky to me. > other clones. The "last clone read" rule may be too confusing. But I > don't see a good, simple, solid solution. I reiterate my idea of providing optional @priority tag in the body of the @thin root. Something like @priority low/high or some number. > Would the problem be simpler if all branches used the same > leoProjects.txt file? Well, perhaps in some ways, but mixing clones > from different branches seems like not such a hot idea :-) Or, just create a new thin file that has stuff of interest to that branch alone. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
