<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 2, 2016 at 1:38 PM, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Not every time you do an activity are you doing work worth
committing. For instance I work with a lot of terminals, that I
reuse and there's no point in committing terminal sessions.</p>
<p>So imho Sugar should not force you to commit if you don't want
to.<br></p></div></blockquote><div><br></div><div>We had long ago talked about letting some activities opt out. Regardless, adding the commit message back with an opt-out button is fine with me, but I still don't understand what problem we are solving. If I understand it, Tony also wants to circumvent the relaunch last instance by default as well. In the case of your Terminal example, it would mean you'd have Terminal instances in your Journal for each time you used the Terminal unless you too the time to go to the Journal and search for a previous instance. I think that makes the spam problem worse, not better.</div><div><br></div><div>-walter</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><p>
</p>
<br>
<div>El 02/06/16 a las 12:36, Walter Bender
escribió:<br>
</div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jun 2, 2016 at 12:34 PM,
Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank"></a><a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">El
02/06/16 a las 11:37, Walter Bender escribió:<br>
<span><br>
><br>
> I don't recall there ever being a 'Don't Save"
dialog. I do recall the<br>
> dialog to enter a "commit message" upon exit. I'm
all for the latter!!!<br>
<br>
</span>Yes the proposal is a 'commit message' with a
'don't commit' option. I<br>
was never a fan of the former but having the option would
change my mind.<br>
<br>
Can you help point Utkarsh to when this was removed?
Thanks!<br>
</blockquote>
<div><br>
</div>
<div>It was sometime before 0.96 because it was in that
release I added the "Write to Journal Anytime" feature.</div>
<div><br>
</div>
<div>But I am confused as to what problem we are solving
here.</div>
<div><br>
</div>
<div>I think we should require commit messages in Sugar the
same way we require them in our own work. But that said,
the decision to commit is made numerous times through out
the lifecycle of an activity, not just at closing. For
example, Turtle, Write, and many others will write
whenever the activity goes to the background. And Turtle
saves whenever you run code. So how does a "don't commit"
option work exactly? </div>
<div><br>
</div>
<div>-walter</div>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div data-smartmail="gmail_signature">
<div dir="ltr">
<div><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div></div>