<div dir="ltr"><a href="http://wiki.sugarlabs.org/go/Gitbackend">Here</a> I have listed functional requirements and put user work flow. Please let me know if any neat is needed. <br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Thanks!!!<a href="http://about.me/shaifaliagrawal" style="text-decoration:none" target="_blank"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="height:30px;font-size:0px"></td></tr><tr><td style="line-height:1;padding:0px;vertical-align:top" align="left" valign="top"><div style="margin:0;font-size:18px;line-height:1;font-weight:bold;color:#333333;font-family:proxima-nova-1,Proxima-Nova,Helvetica,Arial,Sans-Serif">Shaifali Agrawal</div>
<div style="margin:0;margin-top:3px;font-size:12px;color:#2b82ad;font-family:proxima-nova-1,Proxima-Nova,Helvetica,Arial,Sans-Serif">about.me/shaifaliagrawal</div>
</td>
</tr>
<tr>
<td style="line-height:1;vertical-align:top;padding-top:8px" align="left" valign="top">
<div style="text-align:right;background-color:#c5d0e0;height:4px"><img src="http://d13pix9kaak6wt.cloudfront.net/signature/colorbar.png" alt="Shaifali Agrawal on about.me" style="float:right;border:0;margin:0;padding:0;display:block" height="4" width="88"></div>
</td>
</tr>
<tr><td style="height:20px;font-size:0px"> </td></tr>
</tbody></table>
</a>
<br></div></div></div>
<br><div class="gmail_quote">On Mon, Mar 23, 2015 at 1:25 PM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Most if not all of the git size increase is caused by the checked out working copy. That would not happen though. A backend would use a bare repository. A working copy of an entry would only exist for the duration of an activity.<br>
<br>
If it did become a problem, it should be possible to turn off this feature for systems with limited space, like XO-1. I don't think the XO-1 is sufficient reason to avoid git altogether. We have XO-4 now. Sugar must move on, and not be held back by an installed base of XO-1. Let the user decide how to use the space available.<br>
<br>
If the datastore (which is used to store the journal) were to use the same method as it does now for most entries, then there would be no size increase.<br>
<br>
Then, the user might select an entry in the journal for which a git backend is to be used. Once this is done, a history of changes to this entry can be kept.<br>
<br>
On the other hand, this all seems premature. Before the implementation details are debated, describe the user work flow.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</div></div></blockquote></div><br></div>