On 20/06/17 02:40, Edward K. Ream wrote: > > *Summary* > > Leo's existing read logic is at least a decade old. There have been > hints of trouble in the past, but the troubles with git branches are > now intolerable. Happily, git also provides recovery options that did > not exist 10 years ago. > [...] > All comments welcome. >
Is good to see that closer integration with DVCS is finally coming. Some experiments were propossed using Fossil instead of Git, which provides less cognitive and technical overhead, but is less popular. At some point abstracting reading logic DVCS support for Git would enable a more neutral approach that could be used for others, but going with the popular option as a first implementation is wise (is happening now with Git and native DVCS in the Pharo Community). Cheers, Offray -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
