On Mon, Jun 22, 2009 at 1:01 PM, Edward K. Ream <[email protected]> wrote:
> > <<quote snipped>> > >> >> >> The .leo file differs from simple project files of various IDEs in >> that it can have valuable content that's not trivially derived from >> anywhere else. You may want to have it in version control outside you >> normal development tree, but it's still handy to have it somewhere. > > > True, but this is not recommended. I recommend the approach discussed at: > > > http://webpages.charter.net/edreamleo/FAQ.html#how-should-i-use-leo-with-bzr-git-hg-svn-cvs > > where most information is in @thin trees and the "reference" .leo file > changes only when new @thin nodes are added. > > Edward > What do you do about nodes and structure that is shared among multiple @thin trees in that scenario? Also, what about things that should be kept with the code, but are not part of the code itself? (Leo's clones provide a nice facility for associating code and high-level documentation such as business requirements.) --Lucas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
