Lucas,

I recommend using @thin trees.  You need to have the .leo_shadow 
directories under version control, and could ignore the actual shadow 
files if you like (leo will load the file in the .leo_shadow directory 
to recreate the shadow file when needed).

I found @shadow files duplicate the size of the repo, and that @thin 
were easier.

Mike

Lucas Thode wrote:
> Hey all,
>
> I'm putting a fairly new project that's using Leo (@shadow trees) 
> under version control (SVN) for the first time.  I've already put the 
> derived files under VC, so what else do I need to check in? The .leo 
> file? the .leo_shadow stuff? Nothing?
>
> --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
-~----------~----~----~----~------~----~------~--~---

Reply via email to