[Monotone-devel] [bug #28789] Cached workspace files between consecutive executed workspace commands

[Thomas Keller]

Follow-up Comment #1, bug #28789 (project monotone):

>From revision 0db915193923a54f43d91a67688e2fc4f8641683 the situation is now a
little different, but not better for _MTN/options:

If a stdio instance runs and f.e. the branch in _MTN/options changed from
some.branch to some.other.branch, then the first execution of

  l10:get_option6:branche

returns (correctly) some.other.branch, but also directly overwrites
_MTN/options again with the wrong (old) branch some.branch, so that the next
execution of this command returns some.branch again.

We have a little chicken-egg problem here - one the one hand we want to reset
the (global) options for a command back to the original values (so if command
1 changes some global option, command 2 does not suffer its setting and cannot
even undo it, f.e. --ignore-suspend-certs), on the other hand we want the
original options get updated when the "outside" world, f.e. _MTN/options
changes...

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?28789>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/