On Fri, Jan 29, 2010 at 11:34 AM, Gil Shwartz <[email protected]> wrote:
> Again, I'm trying to discuss future code, realizing the limitations of > the current one with respect to "multi source" type of clone. > >> > To summarize, the following are useful options for the user to have: >> > a. De-clone this clone node (making it a regular node and keeping its >> > content version x). >> > b. Split-clone all clone content version x nodes (keeping them as >> > clones with content version x). >> > c. Re-sync this clone node with clone content version y (replacing >> > this node x by y). >> > d. Re-sync all clone content version x nodes with clone content >> > version y (replacing all x by y). >> > e. Re-sync all clone content version y nodes with this clone content >> > (replacing all y by x). We can imagine doing this, provided all these options do not actually impact Leo's data structures in any way. The read code could leave some "error recover" data lying around, for the use, say, of a plugin, but that's about all that can be done, imo. That may be enough to provide the kinds of options you suggest above. If it is, all well and good. 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.
