<html><body bgcolor="#FFFFFF"><div>On 29 Jun 2010, at 19:56, Martin Abente <<a href="mailto:mabente@paraguayeduca.org">mabente@paraguayeduca.org</a>> wrote: </div><div></div><blockquote type="cite"><div>Martin and James, In case you haven't noticed, we know how it could be better and we know how the high level pseudo code would look like. We just can't do it, because we have no more time to spend on this. The backup and restore script are just a little part of this whole patch, and it would be _very_ helpful if someone could actually test it and review the code. Thanks for your comments, hopefully we or someone else will have the time to improve it, in the near future. _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></blockquote> <span class="Apple-style-span" style="font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On Thu, 1 Jul 2010 19:50:02 +0100, Gary Martin <<a href="mailto:garycmartin@googlemail.com" x-apple-data-detectors="true"><a href="mailto:garycmartin@googlemail.com">garycmartin@googlemail.com</a></a>> wrote: <blockquote type="cite">On 1 Jul 2010, at 14:02, Tomeu Vizoso <<a href="mailto:tomeu@sugarlabs.org" x-apple-data-detectors="true"><a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a></a>> wrote: </blockquote><blockquote type="cite"> </blockquote><blockquote type="cite"><blockquote type="cite">On Wed, Jun 30, 2010 at 03:57, Bernie Innocenti <<a href="mailto:bernie@codewiz.org" x-apple-data-detectors="true"><a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a></a>> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">wrote: </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">== New Features == </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">sugar/backup-0001-Volumes-Backup-and-Restore.patch </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">sugar/backup-0002-Journal-XS-backup-and-restore.patch </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">There are concerns about restore deleting new entries since the </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">last backup. I agree, but since nobody seems to have the time to </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">implement and test a more sophisticated procedure, at this time </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">this is the best restore feature we have for Sugar. </blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Do we know any other deployment willing to deploy this? </blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">If we decide to merge it, I think it should be disabled by default and </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">have a gconf setting, because knowingly shipping a feature that causes </blockquote></blockquote><blockquote type="cite"><blockquote type="cite">data loss may not be a good idea. </blockquote></blockquote><blockquote type="cite"> </blockquote><blockquote type="cite">Sounds fair. I was going to suggest making sure there was at least a </blockquote><blockquote type="cite">second user action needed after hitting a backup or restore button (I </blockquote><blockquote type="cite">skimmed through the patch code but couldn't see a conformation warning </blockquote><blockquote type="cite">step). A warning notification with Cancel/Backup, and Cancel/Restore <span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); ">could</blockquote><blockquote type="cite">help avoid some accidents. </blockquote><div> </div>Just posting on this email thread as well. Not being sarcastic here :-p genuine question, is there a trac ticket for this one? Some patches do, some patches don't.<div><span class="Apple-style-span" style="font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.226562); -webkit-composition-frame-color: rgba(77, 128, 180, 0.226562);"> </div><div><span class="Apple-style-span" style="font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Regards,</div><div><span class="Apple-style-span" style="font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">--Gary</div><div><span class="Apple-style-span" style="font-size: medium; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "> </div></body></html>