On Wed, Mar 3, 2010 at 12:42 PM, Ville M. Vainio <[email protected]> wrote: > On Wed, Mar 3, 2010 at 8:01 PM, Kent Tenney <[email protected]> wrote: > >> For starters, the Leo file is optimized for collaborative editing, branching >> merging, versioning ... >> >> That's what Git does. >> >> ... if Leo could provide node=file equivalence. > > There is already @button git-dump in scripts.leo ;-).
Interesting, though I'm not sure how to leverage the Git capabilities without a git-load @button which populates a Leo file with the tree contents. Thanks, Kent > > While using git for maintaining the leo doc seems to open lots of > interesting avenues for exploration, the git-dump like approach > already offers most of the benefits with cheap implementation cost. > > -- > 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. > > -- 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.
