On Tue, 08 Jul 2014 10:36:43 -0400 Jacob Peck <gatesph...@gmail.com> wrote:
> What it could allow is per-node versioning... but there are better > ways of doing that. Kent's work, for example... "versioning Leo nodes with git" 2013-8-28 https://groups.google.com/forum/#!topic/leo-editor/F4k_zCXjtYc "Versioning Leo nodes... with Leo!" 2013-8-29 https://groups.google.com/forum/#!msg/leo-editor/Y-daCfU5C5Y/5pV0Ukgcr0cJ I don't think either of these cover what Kent's trying to do. Cheers -Terry > -->Jake > > On 7/8/2014 10:16 AM, Fidel N wrote: > > could that become some short of collaborative outline editing for > > Leo maybe? > > > > > > On Tue, Jul 8, 2014 at 2:46 PM, Edward K. Ream <edream...@gmail.com > > <mailto:edream...@gmail.com>> wrote: > > > > I've been studying the pro git book: http://git-scm.com/book and > > am now closely studying the internals chapter: > > http://git-scm.com/book/en/Git-Internals > > > > Stimulated by Kent's work with db's, the question arises: is it > > possible to represent a Leo outline as a git object? > > > > I believe the answer is yes, and not just in the trivial sense > > that any content is a blob: > > > > - Every node's gnx, headline, body text and uA (and anything > > else) has a unique (sha-1) hash. > > - We could define (git) tree objects that contain the following > > entries: gnx, headline, body text, uA, parents, children. > > - Empty uA's would be represented by the hash for an empty > > string. > > - Parents and children entries would be other git tree objects. > > > > In this way, we could use git plumbing to build a git tree > > object representing an entire outline, with all the data contained > > in a .leo file. > > > > In other words, even though git is *content* addressable, the > > content can contain gnx's, so that nodes *identities* are > > preserved. > > > > Don't know whether any of this will be helpful in the current > > creative ferment, but I thought I would point it out. > > > > Edward > > -- > > You received this message because you are subscribed to the > > Google Groups "leo-editor" group. > > To unsubscribe from this group and stop receiving emails from > > it, send an email to leo-editor+unsubscr...@googlegroups.com > > <mailto:leo-editor+unsubscr...@googlegroups.com>. > > To post to this group, send email to leo-editor@googlegroups.com > > <mailto:leo-editor@googlegroups.com>. > > Visit this group at http://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "leo-editor" group. > > To unsubscribe from this group and stop receiving emails from it, > > send an email to leo-editor+unsubscr...@googlegroups.com > > <mailto:leo-editor+unsubscr...@googlegroups.com>. > > To post to this group, send email to leo-editor@googlegroups.com > > <mailto:leo-editor@googlegroups.com>. > > Visit this group at http://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
