Hi,
One note of caution. Currently when a Sugar activity resumes from a
Journal object, the activity operates on that object. Therefore, the source
version is destroyed. I think this is not a feature - the activity
should clone the object and give the user the opportunity to rename to
save a new version.
I don't understand the need for git, the Journal is intended to give the
reflective look back within the Sugar interface guidelines.
Currently, the Journal backup is rsync on the datastore. Any design with
git would need to make sure the git versions are also backed up and
restored.
Tony
On 03/20/2015 11:24 PM, sugar-devel-requ...@lists.sugarlabs.org wrote:
The objective of have a git backend is have a versioned
>Journal, where you can store all the intermediate steps for a entry.
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
