On Mon, Jun 22, 2009 at 12:33 PM, Ville M. Vainio <[email protected]>wrote:
> > On Mon, Jun 22, 2009 at 8:24 PM, Steve Zatz<[email protected]> wrote: > > >> Having the .leo file in version control hurts no one ... > > > But what is the reason to have it in version control? In my mind, > > It's a backup thing. If it contains valuable data, it won't be > permanently scorched by rm -Rf . or equivalent. You can call it > foo_steve.leo or whatever if you wish ;-). > > 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
