On Apr 9, 5:33 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> I never dreamed that bzr would make such a difference to the Leo project. It now seems to me that bzr does for backup what Python did for programming. In my white paper about Python, I mentioned Python's safety: http://webpages.charter.net/edreamleo/whitepapers.html#safety Last night I realized the same kinds of remarks apply to bzr. It doesn't matter how many branches are created, or the order in which they are merged. Nothing is dangerous, except possibly not creating branches to hold intermediate work. :-) For example, I have just created a sax branch. It contains last night's work removing all non-sax code from Leo's fileCommands read code. Last night I could just blast away this crucial code. No worries. I was working in the devel branch, but when it became clear that the project was going to take more work, I just pushed what I had to the sax branch. Now I can revert (pull) the devel branch if I like, and work on the sax branch at my leisure. In essence, bzr makes it possible to delay decisions about what branches should, or should not, be created, and decisions about what code is, or is not, safe to release. None of the choices are final: they can always be modified later. The *effect* of bzr is that I can work on multiple branches simultaneously. Never again will I worry about what "should" come first. I'll just do my work, save to branches, and decide later when and how to merge into the ekr-devel or trunk branch. This is my idea of complete safety. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
